Dynamic User Interface Schemes for an Electronic Device Based on Detected Accessory Devices

ABSTRACT

A system may include an electronic device that includes an enclosure having a transparent cover. The electronic device may also include a display positioned below the transparent cover and configured to display a first graphical user interface and a second graphical user interface different from the first graphical user interface, and a touch sensor positioned below the transparent cover and configured to detect touch inputs applied to the transparent cover. The system may also include a protective case that includes a shell defining a cavity and configured to at least partially cover the enclosure of the electronic device when the electronic device is positioned in the cavity, and a near-field wireless communication antenna coupled to the shell and detectable by the electronic device. In response to detecting the near-field wireless communication antenna, the electronic device may be configured to switch from the first graphical user interface to the second graphical user interface.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.17/583,902, filed Jan. 25, 2022, which is a continuation of U.S. patentapplication Ser. No. 17/033,641, filed Sep. 25, 2020, now U.S. Pat. No.11,240,365, the contents of which are incorporated herein by referenceas if fully disclosed herein.

FIELD

The described embodiments relate generally to electronic devices, andmore particularly to electronic devices and accessories that usenear-field wireless communication systems to dynamically alter theoperation of the electronic devices.

BACKGROUND

Handheld electronic devices such as mobile phones and tablet computersprovide numerous functions and features, and use graphical userinterfaces to allow users to interact with and control those functionsand features. For example, handheld electronic devices display inputobjects such as icons, buttons, keys, and other graphical objects withwhich a user may interact to control the devices and their variousfunctions. The devices may also display output objects, such as text orimages, that convey information to the user.

SUMMARY

A system may include an electronic device that includes an enclosurehaving a transparent cover. The electronic device may also include adisplay positioned below the transparent cover and configured to displaya first graphical output and a second graphical output different fromthe first graphical output, and a touch sensor positioned below thetransparent cover and configured to detect touch inputs applied to thetransparent cover. The system may also include a protective case thatincludes a shell defining a cavity and configured to at least partiallycover the enclosure of the electronic device when the electronic deviceis positioned in the cavity, and a near-field wireless communicationantenna coupled to the shell and detectable by the electronic device. Inresponse to detecting the near-field wireless communication antenna, theelectronic device may be configured to switch from the first graphicaloutput to the second graphical output. The first graphical output mayinclude a first background image, and the second graphical output mayinclude a second background image different from the first backgroundimage.

The electronic device may be a mobile phone and the protective case mayhave an exterior surface having a color. The first graphical output mayinclude a group of application icons and have a first color scheme andthe second graphical output may include the application icons and have asecond color scheme. The second color scheme may be different from thefirst color scheme and may correspond to the color of the exteriorsurface of the protective case.

The enclosure may define a back exterior side of the electronic device,a front exterior side of the electronic device, and a peripheralexterior side of the electronic device, the peripheral exterior sideextending from the back exterior side to the front exterior side. Theshell may further define a window region configured to allow a user totouch the front exterior side of the electronic device when theelectronic device is positioned in the cavity, a back wall configured toat least partially cover the back exterior side of the electronicdevice, and a side wall configured to at least partially cover theperipheral exterior side.

The protective case may further include an input system that includes anactuation member configured to be actuated by a user and a passiveantenna. Subsequent to detecting the near-field wireless communicationantenna and in response to the actuation member being actuated by theuser, the passive antenna may become detectable by the electronicdevice. The electronic device may be configured to execute an operationin response to detecting the passive antenna. The passive antenna maynot be detectable by the electronic device when the actuation member isunactuated. The electronic device may further include a camera system,the second graphical output may correspond to an image-captureinterface, and actuation of the actuation member may cause theelectronic device to capture an image using the camera system.

A dock for an electronic device may include a support structureconfigured to position the electronic device in a viewable orientationwhen the dock is on a surface of an object, a near-field wirelesscommunication antenna configured to cause the electronic device todisplay a graphical user interface in response to the electronic devicebeing positioned on the support structure, and an input systemconfigured to wirelessly communicate with the electronic device inresponse to the input system being actuated by a user when theelectronic device is positioned on the support structure. The inputsystem may include an actuation member and a passive antenna, and, inresponse to the actuation member being actuated by the user, the inputsystem may wirelessly communicate with the electronic device using thepassive antenna.

The graphical user interface may be a secondary graphical userinterface, and the electronic device may be configured to switch fromdisplaying the secondary graphical user interface to displaying aprimary graphical user interface in response to being removed from thesupport structure.

The graphical user interface may correspond to an alarm clock functionof the electronic device, and actuation of the input system may causethe electronic device to change a setting of the alarm clock function.The dock may further include a speaker, the graphical user interface maycorrespond to an audio playback function of the electronic device, andactuation of the input system may cause the electronic device to changean operational parameter of the audio playback function. The dock mayfurther include a wireless charging system comprising an output coilconfigured to inductively couple to a charging coil of the electronicdevice when the electronic device is held by the support structure.

A handheld electronic device may include an enclosure, a display, atouch sensor positioned within the enclosure, and a near-field wirelesscommunication system configured to detect when the handheld electronicdevice is in proximity to any one of a set of docking accessories. Whenthe near-field wireless communication system detects that the handheldelectronic device is in proximity to a first docking accessory of theset of docking accessories, the handheld electronic device maytransition from a first mode of operation to a second mode of operationdifferent from the first mode of operation, and, when the near-fieldwireless communication system detects that the handheld electronicdevice is in proximity to a second docking accessory of the set ofdocking accessories, the handheld electronic device may transition fromthe first mode of operation to a third mode of operation different fromthe first mode of operation and from the second mode of operation.

The first docking accessory may be in a first location and the seconddocking accessory may be in a second location different from the firstlocation. Transitioning from the first mode of operation to the secondmode of operation may include transitioning from displaying a primarygraphical user interface comprising a set of application icons todisplaying a first auxiliary graphical user interface comprising a firstset of graphical objects that are relevant to the first location, andtransitioning from the first mode of operation to the third mode ofoperation may include transitioning from displaying the primarygraphical user interface to displaying a second auxiliary graphical userinterface different from the first auxiliary graphical user interfaceand comprising second set of graphical objects that are relevant to thesecond location.

Transitioning from the first mode of operation to the second mode ofoperation may include transitioning from displaying a primary graphicaluser interface to displaying a first auxiliary graphical user interface,and transitioning from the first mode of operation to the third mode ofoperation may include transitioning from displaying the primarygraphical user interface to displaying a second auxiliary graphical userinterface different from the first auxiliary graphical user interface.The first auxiliary graphical user interface may include a firstuser-defined set of graphical objects selected from a group of candidategraphical objects and the second auxiliary graphical user interface mayinclude a second user-defined set of graphical objects selected from thegroup of candidate graphical objects. The first user-defined set ofgraphical objects may include an audio control input object. The seconduser-defined set of graphical objects may lack the audio control inputobject. The first user-defined set of graphical objects may be arrangedon the display according to a user-defined arrangement.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure will be readily understood by the following detaileddescription in conjunction with the accompanying drawings, wherein likereference numerals designate like structural elements, and in which:

FIG. 1A depicts an example system including an electronic device andassociated accessories;

FIG. 1B depicts the device of FIG. 1A and an example accessory in usetogether;

FIGS. 2A-2B depict an example wireless charging system for the device ofFIG. 1A;

FIG. 3A depicts several example protective cases for the device of FIG.1A;

FIGS. 3B-3C depict the device of FIG. 1A being used with an exampleprotective case;

FIGS. 3D-3F depict the device of FIG. 1A being used with another exampleprotective case;

FIGS. 3G-3I depict a device being used with an example removableaccessory;

FIGS. 3J-3L depict a device being used with another example removableaccessory;

FIGS. 3M-3N depict the device of FIG. 1A being used with another exampleprotective case;

FIGS. 30-3P depict the device of FIG. 1A being used with another exampleremovable accessory;

FIG. 4 depicts several additional example devices holders for the deviceof FIG. 1A;

FIG. 5 depicts several additional example protective cases for thedevice of FIG. 1A;

FIG. 6 depicts an example group of candidate graphical objects forcreating user-defined auxiliary graphical user interfaces;

FIG. 7 depicts several example docks for the device of FIG. 1A; and

FIG. 8 depicts example components of an electronic device.

DETAILED DESCRIPTION

Reference will now be made in detail to representative embodimentsillustrated in the accompanying drawings. It should be understood thatthe following description is not intended to limit the embodiments toone preferred embodiment. To the contrary, it is intended to coveralternatives, modifications, and equivalents as can be included withinthe spirit and scope of the described embodiments as defined by theappended claims.

The embodiments herein are generally directed to a system of electronicdevices and electronic device accessories that use near-field wirelesscommunication techniques to dynamically modify or change how a deviceoperates. For example, various different accessories for electronicdevices may each include near-field wireless communication antennas thatallow the accessories to be detected and identified by the electronicdevice. Once a particular accessory is detected near the electronicdevice, the electronic device may change its mode of operation in amanner that is unique to that particular accessory or type of accessory.

Various different types of accessories may be configured to usenear-field wireless communication systems to affect the operationalmodes and/or characteristics of devices that are using thoseaccessories. For example, a protective case for a mobile phone may beconfigured to change the operational mode of the mobile phone in onemanner, while charging docks change the operational mode of the mobilephone in another manner, while an “alarm clock” docking accessorychanges the operational mode of the mobile phone in yet another manner.The change in operational mode may correspond to and/or be accompaniedwith a change in the graphical user interface or graphical output thatis displayed by the mobile phone. For example, when the mobile phone isplaced in a sport-focused protective case, the mobile phone may, withoutadditional user input, replace its primary graphical user interface (orany graphical user interface that is currently active) with asport-focused interface. As another example, when the mobile phone isplaced on a speaker dock, the mobile phone may replace its primarygraphical user interface with a set of audio playback controls. Thegraphical user interfaces that are activated when a device is used withan accessory may therefore be customized to a particular function or setof functions that are relevant to the associated accessory. In somecases, these graphical user interfaces may be simpler than a primarygraphical user interface (e.g., having fewer and/or larger graphicalobjects), which may help facilitate more efficient use of the device andmay be dedicated to a particular function set or operational mode of thedevice.

In some implementations described herein, one or more graphical outputsthat are displayed on the device are changed or switched in response todetecting the protective case. As used herein, graphical outputs may beused to refer to visible output from a display. Graphical outputs mayinclude graphical user interfaces, graphical objects, images, videos,and/or other visible outputs produced by a display. Graphical userinterfaces may include various types of graphical objects, includingicons, menu items, status bars, menus, graphical objects indicatinginformation such as wireless signal strength, time, battery chargelevel, and the like. Graphical user interfaces may also includegraphical outputs such as background images. Graphical objects may bevisually differentiable from other graphical objects, and the boundariesand/or borders of a graphical object may suggest functional distinctionsbetween different graphical objects. For example, the boundary and/orborder of a first icon (e.g., a first graphical object) may visuallydifferentiate the first icon from a second icon, and may indicate to auser that the two icons define different input areas and will, ifselected, cause a device to take different actions.

As used herein, the terms “switch” or “change” a graphical output may beused to refer to a scenario in which one graphical user interface,graphical object, or other displayed item is exchanged with anothergraphical user interface, graphical object, or other displayed item. Theterms “switch” or “change” may also be used to refer to a scenario inwhich a graphical user interface, graphical object, or other displayeditem is modified to produce a visually distinct or visually perceptibleeffect. For example, a background or color scheme of one or moregraphical objects in a graphical user interface may be “switched” or“changed” to appear to have a different color, texture, or othervisually perceptible feature. For clarity, the switched or changedgraphical output may be referred to as a second graphical output eventhough, other than an appearance, the graphical output may represent thesame item or perform the same function when selected.

For the purposes of this disclosure, accessories may include, withoutlimitation, protective cases, gaming cases, camera cases, and docks(e.g., speaker docks, alarm clock docks, charging docks, unpowereddocks, etc.). Cases, such as protective cases, gaming cases, cameracases, may be accessories that are configured to receive an otherwisecomplete device, such as a mobile phone, and may provide additionalfunctionality to the device (e.g., physical protection, appearance,attachment mechanisms, etc.). Such accessories that include near-fieldwireless communication antenna and cause an electronic device to changeor modify the operational mode and/or characteristic of the electronicdevice when the device and the accessory are in proximity to one anothermay be referred to herein as a near-field wireless enabled accessory.

The changing or modifying of the operational mode and/or characteristicsof electronic devices may be facilitated by near-field wirelesscommunications that allow the electronic devices to determine when theyare being used with the accessories. For example, the accessories mayinclude near-field wireless communication antennas, and the devices mayinclude near-field wireless communication systems that can detect whenthe device is in close proximity to the near-field wireless antennas(e.g., the device can detect when it has been installed in, coupled to,placed on, or is otherwise being used with the accessory). The devicemay also receive, from the near-field wireless communication antenna,information about the particular accessory such as a unique identifier.

The near-field wireless communication systems and antennas may beconfigured so that an accessory is detected by a device only when thedevice is sufficiently close that it is substantially certain that thedevice and the accessory are being used together. For example, in thecase of a protective case for a mobile phone, the mobile phone maydetect the presence of the case only once the phone is inserted into theprotective case. In the case of a docking accessory (also referred toherein as a “dock”), the mobile phone may detect the presence of thedocking accessory only once the mobile phone is physically placed on thedocking accessory. Further, the near-field wireless communicationantennas may be passive or un-powered antennas, allowing dynamic devicecustomization to occur even with un-powered accessories. As used herein,passive or un-powered antennas refer to antennas that are notconductively coupled to an electrical power supply of the accessory.Accordingly, a protective case need not have batteries or independentlypowered communications systems (e.g., WIFI or Bluetooth) in order tochange the operational mode or other characteristic of the electronicdevice. In some cases, however, devices may include both un-powerednear-field wireless communication antennas as well as poweredcommunications systems.

By providing a series of different accessories that can each customizethe operation or user interface of a mobile device in a different way,the mobile device may become an even more dynamic, useful tool. Forexample, throughout a day, a user may place a mobile device in a workoutcase for a morning workout, in a charging dock during work, in a kitchendock in the evening, and in an alarm clock dock at night. The conceptsdescribed herein allow the device to automatically transition to aworkout interface when it is placed in the workout case, to a workinterface when it is placed in the charging dock, to a cooking interfacewhen it is placed in the kitchen dock, and to an alarm clock interfacewhen it is placed in the alarm clock dock, among numerous other possibletransitions. The device may also transition back to a main or primaryinterface when it is removed from those docks (or in response to a userrequest regardless of its proximity to an accessory). In this way, thedevice continuously and automatically adapts to its intended use andprovides a tailored user interface to its user.

Further, the device may use other inputs and/or information to determinehow to change or modify its operations when the device is being usedwith a near-field enabled accessory. For example, when the devicedetects that it has been attached to a dock of an exercise bike, it mayalso determine the location of the device. If the location is a firstlocation (e.g., a home location), the device may take a different set ofactions than if the location is a second location (e.g., a fitnesscenter or gym). In the home location, the device may initialize a firstset of user controls, such as a set of media controls for the user'shome media system (e.g., the user's television, stereo equipment, etc.)and a fitness tracking interface, while in the fitness center, thedevice may initialize a second set of user controls, such as the fitnesstracking interface and a set of media controls for a personal streamingservice (e.g., to provide audio to the user's personal headphones). Asanother example, when the device detects that it has been placed on adock in a kitchen, the device may also determine who is using thedevice. If it is a first user, the device may display one set ofinterface elements (e.g., a recipe for a smoothie and an editablegrocery list), and if it is a second user, the device may display asecond set of interface elements (e.g., a recipe for a pasta sauce and aset of media controls for the user's home media system).

Information from any sensor and/or sensor system of a device may be usedto provide additional contextual information about the device, its use,its user, or the like, in order to provide highly customized andtailored user experiences. Such sensors and/or sensor systems mayinclude, without limitation, integrated cameras, GPS or other navigationor location-finding systems, thermal sensors, accelerometers,magnetometers, biometric identification systems (e.g., facialrecognition, fingerprint recognition, voice recognition), biometricsensors (e.g., heart-rate monitors, electrocardiographs, pulseoximeters), or the like. Other types of information not detected by anonboard sensor may also be used to provide additional contextualinformation about the device, its use, its user, or the like. Suchinformation includes, without limitation, current or predicted weatherinformation, date and time information, calendar entries, recentlyopened or closed applications, text or email messages, or the like. Suchinformation may be stored on the device, accessed via a communicationsnetwork, or the like. In some cases, devices use information about anaccessory (from a near-field wireless connection with the accessory)together with additional contextual information (e.g., from a sensorsystem or other information source) to determine how to change, modify,or affect the device's operation. For example, the device may determinewhich application to initiate based on the near-field wirelessconnection and a location of the device. Examples of using additionalcontextual information to determine how to change or affect theoperation of a device being used with a near-field wireless enabledaccessory are provided herein.

FIG. 1A depicts an example system in which an electronic device 100(also referred to herein simply as “device”) may be used with variousdifferent accessories that cause the device 100 to transition betweenoperating modes when the device 100 is used with those accessories. Theelectronic device 100 is an example of an electronic device, such as theelectronic device 800 described herein with respect to FIG. 8 . Asdescribed herein, transitioning between operating modes may includeand/or be accompanied by the initiation and/or termination ofapplications (e.g., initiating or terminating an application in responseto detecting accessories), changes in the graphical user interface orgraphical output displayed by the device 100 (e.g., changes in thecolor, content, appearance, size, icons, or information of a graphicaluser interface), changes in device settings (e.g., alert volume, hapticor tactile output strength, screen brightness), or the like.Transitioning between operating modes (or between different graphicaluser interfaces or other graphical outputs) may or may not include or beaccompanied by a visual animation, sequence, or other graphical effectindicating or occurring during the transition.

The device 100 shown in FIG. 1A is a mobile phone (e.g., a smartphone),but this is merely one representative example of a device that may beused in conjunction with the ideas disclosed herein. Other exampledevices include, without limitation, music/media players, tabletcomputers, laptop computers, wearable electronic devices, watches (e.g.,mechanical, electrical, or electromechanical), and the like.

The device 100 includes an enclosure 102 that defines the exteriorsurfaces of the device 100. The enclosure 102 may include, for example,a housing member 103 that defines a back exterior side of the device 100(e.g., back side 201, FIG. 2 ), a front exterior side of the device 100,and a peripheral exterior side 131 of the device 100, the peripheralexterior side extending from the back exterior side to the frontexterior side. The housing member 103 may be a single piece of material(e.g., a monolithic component), or multiple discrete components. Theenclosure 102 may also include a transparent cover 105 that covers orotherwise overlies a display 104 and/or a touch sensitive surface (e.g.,a touchscreen) of the device 100, and may define a front exterior frontsurface of the device 100. The display 104 is configured to displaygraphical outputs, and the graphical outputs may be visible through thetransparent cover 105 or at least a region of the transparent cover 105.The transparent cover 105 may also define one or more openings to allowinternal components such as microphones, cameras, speakers, sensors, andthe like, to have access to the surrounding environment of the device100. The device 100 may also include a touch sensor that is configuredto detect touch events or touch inputs applied to the transparent cover105. The touch sensor may be integrated with the display or otherwiseconfigured to provide touchscreen functionality.

The device 100 may include a near-field wireless communication system106 that is configured to wirelessly detect when the electronic deviceis in proximity to any one of a group of near-field wireless enabledaccessories. The near-field wireless communication system 106 may beconfigured for any suitable type or protocol of near-field wirelesscommunications, including but not limited to near-field communications(“NFC”) protocols, radio frequency identification (“RFID”) protocols, orany other suitable type or protocol. For example, the near-fieldwireless communication system 106 (and indeed any near-field wirelesscommunication system, antenna, or other component described herein) maybe configured to operate in accordance with applicable standards, suchas ISO/IEC 14443, FeliCa, ISO/IEC 18092, ISO/IEC 21481, ISO/IEC 13157,or the like.

In some cases, the near-field wireless communication system 106 isconfigured to detect the presence or proximity of passive or un-poweredantennas that are incorporated in the accessories. As such, thenear-field wireless communication system 106 may be separate from othercommunication systems in the device 100, such as Bluetooth, WIFI, orcellular communications systems, and may be configured to communicateover a limited range (e.g., the near-field wireless communication system106 may only detect a near-field wireless antenna when they are withinabout 10 cm from each other).

The device 100 may include physical inputs, such as a button 108, withwhich a user can interact to control operations of the device 100. Theparticular function of the button 108 may be changed based on theaccessory with which the device 100 is associated at a given time. Forexample, as described herein, in a primary operating mode, the button108 may serve to activate or deactivate the screen of the device 100. Ina second operating mode, such as when the device 100 is in a caseintended for capturing photographs, the button 108 may operate as ashutter button to capture an image. While the device 100 is shown havingone button 108, this is merely representative and the device 100 mayinclude more or different input mechanisms, including for exampleseparate volume control buttons, fingerprint sensors, rotatable inputmembers, keys, a keyboard, or the like. The device 100 may also includea wireless charging system, described with respect to FIG. 2 .

The device 100 may also include various additional internal componentsand structures, such as sensor(s), memory, processor(s), controlcircuitry, a battery, circuit board (s), a frame or other supportingstructure, antenna(s), or the like. The device 100 may also includefront and/or rear facing camera systems (e.g., a rear-facing camera 214,FIG. 2 ) that can capture images and/or video of external subjects. Thecamera systems may include lenses, image sensors, focusing and zoomingmechanisms, flashes, and any other suitable components.

Additional or different components may also be positioned within theenclosure 102 of the device 100. The device 100 may also include varioussystems and/or components that can receive information from or about auser or the user's surroundings (e.g., touchscreens, microphones,biometric sensors, GPS systems). It is well understood that the use ofpersonally identifiable information (such as information from or about auser or the user's environment and that is stored on or accessible by adevice) should follow privacy policies and practices that are generallyrecognized as meeting or exceeding industry or governmental requirementsfor maintaining the privacy of users. In particular, personallyidentifiable information data should be managed and handled so as tominimize risks of unintentional or unauthorized access or use, and thenature of authorized use should be clearly indicated to users.

The system shown in FIG. 1A also includes various types of accessoriesthat can be used with the device 100. For example, FIG. 1A includesprotective cases 112, docks 114, a dock 116 with auxiliary input systems117, a speaker dock 118, and protective cases 120 with auxiliary inputsystems 121. As described herein, the device 100 may be useable witheach of these accessories (as well as others not shown in FIG. 1A), andas the user switches from one accessory to another, the device 100 maydynamically switch to a different operational mode, present a differentgraphical user interface or graphical output (e.g., present a graphicaluser interface having different content or a different appearance, coloror the like), change a device setting, or otherwise operate in a mannerthat is tailored to the particular accessory with which the device 100is being used. Docks, such as the docks 114, may include stand-aloneaccessories as well as docks that are integrated into other devices,such as exercise equipment (e.g., bicycles, rowing machines, ellipticalmachines, stair-climbing machines, or the like), vehicles, musicalequipment (e.g., guitars, amplifiers, keyboards, etc.), or the like. Thedocks 114 are shown with optional ledges 115 that support or prop thedevice 100 in a convenient viewing position. In some cases, the docks114 may lack the ledges 115, and the device 100 may be retained to thedock 114 and/or maintained in a particular orientation or position usingmagnetic attachment features in the dock 114 and the device 100.

Each accessory may include a near-field wireless communication antenna110 (also referred to herein simply as “antenna”) that is detectable bythe near-field wireless communication system 106 of the device 100. Asused herein, an antenna may be detectable insofar as the antenna ornear-field wireless communication circuitry is capable of producing anelectrical response when probed or polled by a wireless detection deviceor circuitry. For example, the antenna may produce a distinct orrecognizable disturbance or other response to an electromagnetic fieldproduced by another device or circuit, thereby rendering the antennadetectable. Further, as used herein, a near-field wireless communicationantenna being detectable indicates that the near-field wirelesscommunication antenna may be operable to trigger, initiate, or otherwisecause a response in a near-field wireless communication system of adevice, where the response indicates that the near-field wirelesscommunication antenna is in the presence and/or proximity of the device(e.g., within a threshold distance).

When the device 100 detects that it is being used with one of theaccessories in FIG. 1A, for example because it is within a shortdistance of an accessory (e.g., less than about 10 cm), the detectedantenna 110 causes the device 100 to change a mode of operation. As usedherein, changing a mode of operation may refer to or include changing agraphical output of the device (e.g., temporarily or permanentlychanging a color scheme of some or all of a graphical user interface,changing between different graphical user interfaces, initiating thedisplay of graphical objects), changing one or more device settings, orcombinations of these. To facilitate this functionality, each antenna110 may include some identifier or other information that uniquelyidentifies that accessory (or that type of accessory) or may otherwisebe configured to uniquely modify the operation of the device 100. Inthis way, the operation of the device 100 may dynamically change as auser changes from accessory to accessory.

The antennas 110 may be any suitable type of antenna that is detectableby the near-field wireless communication system 106 of the device 100.For example, the antennas 110 may be NFC antennas, RFID antennas, or thelike. In some cases, the antennas 110 may be passive or un-poweredantennas. Accordingly, the accessories need not be powered or includebatteries or other power sources to cause the device 100 to change itsoperational mode. This may allow accessories to be smaller, thinner,lighter, and more portable than they would be if they required powersources. In some cases, an antenna 110 may be powered by a power sourceinternal to or otherwise connected to an accessory. Also, accessoriesthat use power for other purposes (e.g., speakers, amplifiers, etc.) mayuse passive or un-powered antennas despite the availability of power atthe accessory.

The near-field wireless communication antennas 110 may be positioned inthe accessories so that they are aligned with or otherwise suitablylocated so that they can be detected by the near-field wirelesscommunication system 106 when the device 100 is being used with theaccessory. Thus, for example, when the device 100 is installed in aprotective case 112, the near-field wireless communication antenna 110of that case may be substantially aligned with the near-field wirelesscommunication system 106 of the device 100 (e.g., within about 2 cm, orabout 1 cm). The antenna and near-field wireless communication system106 may be similarly aligned when the device 100 is placed on a dock114, 116, or 118.

As described, the device 100 may dynamically change its operational modewhen it is used with different accessories. In some cases, changingoperational modes includes changing between different graphical userinterfaces. FIG. 1B depicts the device 100 displaying a primarygraphical user interface 128 when the device 100 is not being used withan accessory (when it is being used with an accessory that causes thedevice 100 to display the primary graphical user interface 128), anddisplaying a different graphical user interface 130 when the device 100is being used with an accessory 129 (shown in this example as a dock).

The primary graphical user interface 128 may include selectable icons(e.g., application icons that, when selected, cause applications to beexecuted and/or initialized, or otherwise cause graphical userinterfaces associated with the applications to be displayed) or othergraphical objects that correspond to applications or other functions ofthe device 100. The primary graphical user interface 128 may alsoinclude status bars, menus, graphical objects indicating informationsuch as wireless signal strength, time, battery charge level, and thelike. The primary graphical user interface 128 may be automaticallydisplayed when the device 100 is turned on, and may be considered thetop level graphical user interface of the device 100 (or the highesthierarchical level of a multi-level graphical user interface scheme).The primary graphical user interface 128 may also be referred to as a“home screen,” and may be a main starting interface for an operatingsystem of a device. The primary graphical user interface 128 may alsohave a color scheme, which may refer to the color or colors ofbackground images, borders, screen areas, icons, or the like. As usedherein, a secondary graphical user interface may refer to any graphicaluser interface other than the primary graphical user interface.

When the device 100 is placed on an accessory and is positioned by theaccessory so that the device 100 can be seen and interacted with, thedevice 100 may change from the primary graphical user interface 128 toanother graphical user interface. For example, as shown in FIG. 1B, whenthe device 100 is placed on an accessory 129, the device 100 may changefrom the primary graphical user interface 128 to a second graphical userinterface 130 that is different than the primary graphical userinterface 128. The second graphical user interface 130 is merely one ofnumerous possible examples of graphical user interfaces that aredifferent from the primary graphical user interface 128 and to which thedevice 100 may switch in response to the device 100 being used with anaccessory. The change from the primary to the second graphical userinterface may be triggered by the device 100 detecting the near-fieldwireless communication antenna in the accessory 129.

The second graphical user interface 130 may have a different set oficons, inputs, outputs, or other types of graphical objects as comparedto the primary graphical user interface 128. For example, the secondgraphical user interface 130 lacks the application icons of the primarygraphical user interface 128, and instead includes other graphicalobjects, such as graphical objects 132 and 134. The graphical object 132may be a “world clock” graphical object (e.g., displaying the times ofmultiple time zones), and the graphical object 134 may be an “audiocontrol” graphical object (e.g., displaying now-playing information andincluding audio control affordances such as play, pause, skip forward,skip backwards, etc.). Accordingly, the second graphical user interface130 includes different graphical content and provides different devicefunctions than the primary graphical user interface 128. The device 100may automatically change back from the second graphical user interface130 to the primary graphical user interface 128 when the device 100 isremoved from the dock 129, or in response to a user input received whilethe device 100 is on the dock 129.

FIGS. 2A-2B illustrate a wireless charging system for the device 100.FIG. 2A, for example, shows a back view of the device 100 and a chargingdock 200 that is configured to wirelessly charge the device 100 when thedevice 100 is placed on the charging dock 200. FIG. 2B illustrates thedevice 100 positioned on the charging dock 200 in a chargingconfiguration (e.g., with the back surface of the device 100 resting onthe upper surface of the dock 200).

The device 100 includes a charging coil 206 within the device 100 andconfigured to inductively couple to an output coil 210 of the chargingdock 200 to charge the device 100. More particularly, the output coil210 of the charging dock may produce an electromagnetic field, which inturn induces a current in the charging coil 206 of the electronicdevice, and the induced current may be used to recharge the device'sbattery.

The device 100 may include a set of magnetic attachment features, suchas magnets 202, that are configured to facilitate alignment andretention of the device 100 to the charging dock 200. The charging dock200 may include a set of complementary magnets (or ferromagneticmaterials) 204 that are attracted to the magnets 202 to furtherfacilitate alignment and retention of the device 100 to the chargingdock 200. For example, the magnets 202 and complementary magnets (orferromagnetic materials) 204 may be configured so that when the device100 is brought into close proximity of the dock 200 by a user (e.g.,within 2 cm, 1 cm, or another suitable range), the magnets 202 andcomplementary magnets 204 pull the device 100 towards the dock 200 andinto a position that aligns the output coil 210 of the dock 200 with thecharging coil 206 of the device 100. The magnetic attraction may alsoprovide a retention force to hold the device 100 in the aligned positionand prevent the device 100 from slipping off the dock 200 duringcharging. While FIG. 2A describes the device as including magnets 202and the dock 200 as including magnets or magnetic materials 204, it willbe understood that any materials or combinations of materials that aremagnetically attracted to one another may be used in either the device100 or the dock 200. Further, the magnets and/or magnetic materials maybe arranged so that the device 100 magnetically couples to the dock 200in only one orientation. This may further help prevent misalignment andhelps ensure that the wireless charging function can operateefficiently. In some cases, other techniques for aligning the device 100with the dock 200 may be used instead or in addition to the magnets,such as alignment pins and recesses, clips, complementary shapedsurfaces, or the like.

In some cases, the dock 200 may include a near-field wirelesscommunication antenna, similar to the antennas 110 described withrespect to FIG. 1A. In this way, the device 100 can detect when it hasbeen placed on or is otherwise being held by the dock 200 using the samenear-field wireless communication system that it uses to detect thepresence of other accessories. (In other cases, the device 100 cancommunicate with the dock 200 using the charging and output coils or viaanother wireless protocol or technique.) When the device 100 detectsthat it is positioned on the dock 200 via the near-field wirelesscommunication system, it may change its mode of operation in a way thatis tailored to the dock 200. For example, as shown in FIG. 2A, thedevice 100 may display a graphical object 211 on the display 104. Thegraphical object 211 may be an overlay over a blank screen or over aprimary graphical user interface of the device 100. The graphical objectmay include inputs and outputs that are contextually related to the dock200 and/or the charging operation provided by the dock 200. For example,as shown the graphical object 211 displays a name or description of thedock 200 (e.g., “Bedroom Charger”), as well as inputs 212 that maycontrol one or more aspects of the charging operation. For example, theinputs 212 may allow the user to select different charging modes ordifferent power consumption modes of the device 100.

Other inputs and outputs may also be included instead of or in additionto those shown in FIG. 2B. For example, the graphical object may includeinputs and outputs that are relevant to a room where the dock 200 islocated. As used herein, a graphical object or graphical user interfacemay be considered relevant to a location, room, accessory, or the like,if the graphical object or graphical user interface provides access tofunctions or information that are germane to a context of the location.Thus, for example, if the dock 200 is in a bedroom, the graphical objectmay include an input for activating or deactivating an alarm. If thedock 200 is in a living room, the graphical object may include an inputfor controlling audio playback of the device 100 or a connected audiosystem (e.g., a home stereo or other device). If the dock 200 is in akitchen, the graphical object may include a recipe interface and one ormore timers. If the dock 200 is in a music room, the graphical objectmay include audio controls and a musical notation interface. In someimplementations, an association of an accessory (e.g., a dock) with aparticular room is based on an assignment of the accessory to a virtualroom in a smart home platform. A smart home platform may includenumerous virtual rooms or environments, and devices and/or smartaccessories may be associated with particular ones of the rooms and/orenvironments. For example, devices such as a television, audio system,and wirelessly-controllable lights may be assigned to a “living room”environment. In some implementations, a dock (e.g., the dock 200) isalso associated with or assigned to the “living room” environment in thesmart home platform. Accordingly, in some implementations, in responseto being placed on the dock in the living room, the device detects thatthe dock is associated with the “living room” environment, and displaysgraphical objects that are configured to control the devices assigned tothe “living room” environment (e.g., the television, audio system, andlights that are in the living room).

While FIGS. 2A-2B show a wireless charging system incorporated in adedicated charging dock, wireless charging systems analogous to thosedescribed with respect to FIGS. 2A-2B may be incorporated into the otheraccessories described herein. For example, a protective case may includea supplemental battery and an output coil to charge the device 100 whenthe device 100 is inserted into the case. Similarly, an output coil andalignment magnets may be incorporated into a speaker dock or alarm clockdock to allow the device 100 to charge when the device 100 is positionedon the dock. Also, wireless charging systems may be incorporated into astand-alone battery accessory that is configured to attach to the deviceand wirelessly charge the device from the battery. An example batteryaccessory is described herein with respect to FIGS. 3J-3L.

As described above, a device 100 may use a near-field wirelesscommunication system to detect that it is being used with an accessory,and to identify that particular accessory. Further, because near-fieldwireless communication antennas do not need to be powered in order tocommunicate with or be detectable by the near-field wirelesscommunication system of a device, even simple accessories such asprotective cases and simple device stands can trigger the device tochange its mode of operation or otherwise modify its behavior. FIG. 3Aillustrates several examples of protective cases for a device, such asthe device 100. The protective cases shown in FIG. 3A may be embodimentsof the protective cases 112 in FIG. 1A. Each protective case in FIG. 3Amay include a near-field wireless communication antenna 110, but maylack other circuits or components that interact with the device 100.Thus, even a simple protective case that appears to be nothing more thana single-piece of plastic or rubber may cause the device 100 to changeits operation in a different or unique way.

With reference to FIG. 1A, the protective cases in FIG. 3A may eachinclude a shell 124 that defines a cavity 125 in which the device 100may be positioned. The shell 124 may be configured to at least partiallycover the enclosure of the device 100 when the device 100 is positionedin the cavity 125. The shell 124 may further define a back wall 122 thatis configured to at least partially cover the back exterior side of theelectronic device (e.g., side 201, FIG. 2A) and a side wall 127configured to at least partially cover the peripheral exterior side 131of the device 100. The shell 124 may also define a window region 126configured to allow a user to touch the front exterior side of theelectronic device (e.g., the transparent cover 105) when the device 100is positioned in the cavity 125. The window region 126 may be an openarea such that the protective case covers all or substantially all ofthe back and side surfaces of the device 100, but leaves the transparentcover 105 substantially uncovered (e.g., such that more than 50%, 60%,70%, 80%, 90%, 95%, or 99% of the front surface of the transparent cover105 is uncovered).

The walls of the shell 124 (e.g., the back wall 122 and the side wall127) may be relatively thin. For example, in some cases, each of thewalls of the shell 124 have a thickness less than about 4 mm, about 3mm, about 2 mm, about 1.5 mm, about 1 mm, or any other suitabledimension. The shell 124 may increase the overall size of the device(e.g., the combined size of the shell with the device installed) by asmall enough amount that the primary functionality of the device 100 isnot fundamentally altered as a result of installing the device 100 inthe protective case. For example, if the device 100 is a mobile phonethat may be held and operated by a user's hand (e.g., a single hand),the device 100 the same or substantially the same use and/or handlingcharacteristics may be preserved when the device 100 is in theprotective case (e.g., it can still be held and operated by one hand).If the device 100 is a tablet that may be held and operated by one ortwo hands, it may be held and operated in the same or similar way evenwhen it is inserted in the protective case.

Each protective case in FIG. 3A may also include a near-field wirelesscommunication antenna 110 coupled to its shell and configured to causethe device 100 to switch from displaying the first graphical userinterface (or graphical output) to displaying a different graphical userinterface (or graphical output) in response to the electronic devicebeing positioned in the cavity. FIG. 3A shows how various differentexamples of protective cases may switch the graphical user interface ofthe device 100. For example, the device 100 in FIG. 3A that is not in aprotective case is shown displaying a first graphical user interface310. The first graphical user interface 310 may be a default or primarygraphical user interface, such as the primary graphical user interface128, FIG. 1B. In some cases, this graphical user interface 310 maydisplay selectable icons (e.g., application icons that, when selected,cause applications to be executed and/or initialized, or otherwise causegraphical user interfaces associated with the applications to bedisplayed) or other graphical objects that correspond to applications orother functions of the device 100. The first graphical user interface310 may also have a background image 311. The background image 311 mayalso be referred to as a wallpaper, and may be an image that isgraphically behind the application icons of the graphical userinterface. In some cases, the first graphical user interface 310 may actprimarily as an application selection screen. (The device 100 may alsohave a “lock screen” or “wake screen” that is displayed when the displayis active but the device 100 is locked. The lock screen may also have abackground image, which may also be referred to as a wallpaper.

The case 300 may be configured to cause the device 100 to ceasedisplaying a first graphical output (e.g., the first graphical userinterface 310) and instead display a second graphical output 312 that isdifferent than the first graphical output. As used herein, a secondgraphical user interface or graphical output may refer to any graphicaluser interface or graphical output that is different from the firstgraphical user interface or graphical output.

When the device 100 is placed in the case 300, the near-field wirelesscommunication system 106 of the device 100 detects the near-fieldwireless communication antenna of the case 300 in close proximity to thedevice 100 (e.g., within about 10 cm, 5 cm, 2 cm, or the like), andreceives information from or about the case 300 from the antenna. Theantenna may communicate an executable command to the device 100, or itmay communicate data that the device uses to select or lookup a commandor routine or otherwise determine how to change its operation.

The graphical output 312 that is initiated by the case 300 may includethe same application icons and provide the same functions as the firstgraphical user interface 310, but have a different background image 313.Thus, when the user installs the device 100 into the case 300, thedevice 100 may automatically transition to a different background image.In some cases, the different background image 313 is a modified versionof the background image 311. For example, a hue, saturation, colorbalance, or other image property of the background image 311 may bemodified to produce the different background image 313.

The different background image 313 may relate in some way to the case300. For example, if the case 300 is blue, the background image 313 maybe blue, or if the case 300 has a rainbow decoration on it, thebackground image 313 may be a rainbow. Accordingly, the graphical userinterface 310 may change or morph to graphically match or coordinatewith the case 300. In this way, a user can switch between cases havingdifferent colors, designs, appearances, or the like, and the appearanceof the graphical output of the device 100 will automatically changebased on the case to which it is coupled.

In addition to or instead of changing the background image, the device100 may display a second graphical output that includes the same iconsand background image as a primary graphical user interface, but has adifferent color scheme. A color scheme for a graphical user interfacemay include particular colors for backgrounds, application icons, statusbars, informational icons, and the like. The color scheme of the secondgraphical output may match or otherwise correspond to a color of anexterior surface of accessory (e.g., the case 300) in which the device100 is installed. For example, if the accessory is yellow, the secondgraphical output may include graphical elements that have the same orsimilar yellow color as the case. Notably, these elements may have adifferent color when the device 100 is not installed in the case. Insome cases, at least one graphical element of the second graphicaloutput has the same color as the accessory.

Other changes to the graphical user interface 310 (or other graphicaloutputs displayed by the device 100) are also contemplated. For example,instead of or in addition to switching to a different background image,the device 100 may change the arrangement of its icons, or the contentor appearance of a lock screen, change an overall color scheme of thegraphical user interface and/or background image, or the like.

Another case, such as the case 302, may have an antenna that causes thedevice 100 to transition from the first graphical user interface 310 toyet another graphical user interface 314 (e.g., a second graphical userinterface). The graphical user interface 314 may be a restrictedenvironment that reduces or otherwise changes the number or type ofavailable application icons, optionally changes the size of the icons,and locks the interface so that a user cannot leave the restrictedenvironment without a password or other type of authentication. Inaddition to changing the graphical user interface, other aspects of thedevice operation may be modified or changed. For example, notifications(e.g., ringer sounds, message previews, etc.) may be turned off orchanged to a different mode (e.g., where message content previews arenot displayed). As another example, access to media stored on the device100 may be restricted or limited, such as restricting movies or songsbased on a rating. In this way, the case 302 may be especially suitedfor use when the device 100 is being given to a child or friend fortemporary use, where the owner of the device 100 may wish to limitaccess to certain applications or functions.

Where the case 302 acts as a child-focused case, the case 302 itself mayinclude physical features that may be useful for a device being used bya child. For example, the case 302 may have extra padding or otherprotection to prevent damage during falls, sealing to prevent damagefrom spills, clear screen covers to prevent damage to or soiling of atransparent cover, grips or other features to facilitate being held bysmaller hands, or the like.

Another example case 304 may have an antenna that causes the device 100to display a graphical user interface or other graphical object that iscoordinated with a physical feature in the case itself, such as anopening in the case. For example, the case 304 includes a front cover316 that a user can open or close over the front of the device 100. Thefront cover 316 may include a window 318 that allows a portion of thedisplay of the device 100 to be viewed when the front cover 316 isclosed. When the device 100 detects that it is being used with the case304 and that the front cover 316 is closed, it may transition from thefirst user interface 310 to another graphical user interface 320 thatincludes a graphical object 322 that is positioned so that the graphicalobject 322 is aligned with and/or visible through the window 318. Thegraphical object 322 as shown includes the current time and weather,though any other information or image may be included instead of or inaddition to that shown. Further, the graphical object 322 may be remaindisplayed even when the front cover 316 is closed and after the displayof the device 100 would otherwise have turned off (e.g., to save power).The device 100 may detect that the front cover 316 of the case 304 isclosed using any suitable technique. For example, the device 100 maydetect that the front cover 316 is closed by detecting that afront-facing camera has been occluded, using a second near-fieldwireless communication antenna in the front cover 316, or any othersuitable technique.

Because the case 304 has a front cover 316, the device 100 may be moreoccluded or covered when it is in the case 304 than it would be inother, open-front cases (e.g., the case 300). Accordingly, when thedevice 100 detects that it is inside the case 304, it may change othersettings or functions of the device as well. For example, it mayincrease an alert volume to account for the muffling or volumeattenuation of the case 304. As another example, the device 100 maydecrease an alert volume or turn off alerts entirely, as the user mayuse the case 304 when they intentionally want to silence the device 100.The device 100 may also change how it provides graphical or visualnotifications, such as by displaying them in the area of the window 318so that they are visible when the front cover 316 is closed. Indeed, aswith any other accessory described herein, the user may customize howthe device 100 changes in operation when it is used with an accessory.For example, the user may select what graphical user interface shouldreplace the primary user interface (e.g., an array of applicationicons), what devices settings should change, and the like. While thecase 304 is shown as having a front cover that can open and close, othertypes of cases may have windows and operate in a manner similar to thecase 304 (e.g., a sleeve-type case with a window on one side of thesleeve).

Another example case 306 may be designed to hold the device 100 duringexercise or other physical activity. The case 306, for example, includesa strap 326 for attaching the case 306 and device 100 to a user (e.g.,to the user's arm or wrist). When the device 100 detects that it hasbeen inserted into the case 306 (e.g., when the device 100 detects thatit is close proximity to the antenna of the case 306), the device 100may transition to a graphical user interface 324 that is tailored foruse during exercise. For example, because devices such as smartphonesare often used as audio players during exercise, the graphical userinterface 324 may include large audio control buttons that are easy tosee and press even during exercise (e.g., buttons that are responsive totouch inputs in an area about one square inch or greater). The device100 may also suggest music or audio (e.g., a workout playlist) inresponse to detecting the case 306. The device 100 may also change adevice setting to accept or respond to different types of inputs than itdoes in a normal operating mode. For example, the device 100 may beconfigured to skip a song when a user knocks on or bumps the device 100,and change a volume of an audio output when the user swipes the palm oftheir hand up or down along the front surface of the device. The device100 may change its settings to respond to other types of inputs as well.

While FIG. 3A illustrates four example cases that may trigger devicechanges using a near-field wireless communication antenna, other typesof cases may also be provided. For example, a case for use when camping,hiking, or other outdoor activities may be configured to cause thedevice 100 to enter a power-saving mode or change device settings tohelp conserve power (e.g., reducing screen brightness, turning offcellular radios and WIFI radios, or the like). Such a case may alsoreplace a conventional lock screen or the primary graphical userinterface with a set of icons for features or applications that arerelevant to outdoor activities. For example, the device 100 may displaylarge buttons to activate a flashlight function, a compass function, amap or positioning application, and a weather application. As notedabove, the particular buttons that are displayed may be selected by auser based on his or her preferences when using that particular case.

As another example, a rugged case may be provided for when the device100 is being used in work environments or during outdoor activities suchas hiking, camping, fishing, boating, skiing, rock climbing, or thelike. Such a case may be ruggedized or otherwise be configured toprovide a greater degree of physical protection to the device, and maybe configured to cause the device 100 to replace a conventional lockscreen or the primary graphical user interface with a set of icons forfeatures or applications that are relevant to a particular activity orwork environment. For example, the device 100 may display buttons toactivate a flashlight function, a level function, a camera application,and a walkie-talkie function. As noted above, the particular buttonsthat are displayed may be selected by a user based on his or herpreferences when using that particular case.

As another example, a case may cause the device to change a backgroundimage or wallpaper to match or coordinate with a separate object. Forexample, a case may change a background image or wallpaper to match orcoordinate with the fabric of a handbag, backpack, purse, or otherobject that the device and case are being used with. If the case isintended to be used when the device is being carried in a bag, backpack,or purse, the case may also cause the device to increase a ringer volumeand/or a tactile notification amplitude to help a user hear or feeldevice notifications through the bag.

FIGS. 3B-3C illustrate an example of the device 100 being used with anaccessory case 330, in which the device 100 displays, on its display104, a color effect in response to being placed in a cavity 331 of aprotective case 330. In particular, as described herein, the device 100detects, with its near-field wireless communication system, that it isin close proximity to the case 330, and receives information about thecase to determine what color effect to display.

FIG. 3C depicts an example color effect 333 that may be produced inresponse to the device 100 detecting that it is being used with the case330. The color effect depicted in FIG. 3C may appear as a wash of colorthat sweeps across the display 104. The color effect 333 may be anyvisible change in a characteristic of the graphical output of thedisplay 104. For example, if the display 104 is displaying a backgroundimage, the color effect 333 may be a change in the hue, tint, shade,tone, saturation, etc., of the background image. The color effect mayalso be an image, pattern, or the like. The color effect 333 may have avisual relevance to the color or use of the protective case 330. Forexample, the color effect 333 may match or be similar to the color ofthe case 330. As another example, the color effect 333 may have acontextual relevance to the use of the case, such as a ruggedized casefor outdoor use causing the color effect 333 to have a camouflageappearance.

Returning to FIG. 3C, at time to, the color effect 333 may appear on thedisplay 104. At time t₁, the color effect 333 (a border of the colorchange) has moved a distance across the display 104, and at time t2, thecolor effect 333 has moved fully across the display 104. This may be theend of the color effect 333 (e.g., the color change persists until thedevice 100 is removed from the case or another event occurs), or thecolor effect 333 may continue with additional changes. For example, the“wash” of color may fade away or continue to move across the display 104until it is gone and the original, unaltered graphical output (e.g.,before time to) is once again displayed by the display 104. In caseswhere the color effect 333 (e.g., the change of color of the graphicaloutput) persists until the device 100 is removed from the case 330, thecolor effect animation shown in FIG. 3C may be reversed in order toreturn the graphical output to the original, unaltered color (e.g., thecolor effect may animate from t2 to to, instead of from to to t2).

The color effect 333 shown in FIG. 3C may be displayed while othergraphical objects or graphical user interfaces are being displayed bythe display 104. For example, the display 104 may display iconsassociated with a main or primary user interface of an operating systemof the device. The icons may appear to be in front of (or on top of) abackground image. The color effect 333 may affect any portion or segmentof the graphical output on the display 104. For example, the coloreffect 333 may result in visual changes to both the background image andthe icons of a graphical user interface, or it may result in visualchanges to the background image but not the icons of a graphical userinterface, or to the icons but not the background image. The coloreffect 333 may also be displayed in conjunction with user interfacesother than the main or primary user interface. For example, the coloreffect 333 may be displayed while a graphical user interface of anapplication (e.g., a program that is executed by or on the operatingsystem) is being displayed.

The graphical user output that is displayed when the color effect 333 isnot present may be considered a different graphical output than thatwhich is displayed when the color effect 333 is present. Stated anotherway, when the color effect 333 is not present, the device may beconsidered to be displaying a first graphical output, and when the coloreffect 333 is present (even transiently), the device may be consideredto be displaying a second graphical output. These are merely examples ofthe ways in which a color effect 333 may affect the appearance of thegraphical outputs on the display 104, and others are also contemplated.

FIG. 3D illustrates an example of the device 100 being used with anaccessory case 334, in which the device 100 displays a graphical outputthat is coordinated with a physical feature in the case 334 itself, suchas an opening in the case. For example, similar to the case 304, thecase 334 defines a window 336 that allows a portion of the display 104of the device 100 to be viewed when the device 100 is in the case 334.When the device 100 detects that it is being used with the case 334(e.g., using the near-field wireless techniques described herein), thedevice 100 may transition from displaying a first graphical output 337(which may be main or primary graphical user interface, a graphical userinterface of an application, or the like) to displaying anothergraphical output, such as a graphical object that is aligned with and/orvisible through the window 336.

The case 334 may define an opening 335 along a side of the case 334 toallow the device 100 to be slid into the case 334. The opening 335 maybe the only opening that is configured to allow the device to be putinto the case 334. While the opening 335 is shown on the side of thecase 334 that has the smallest area, the opening 335 may be along adifferent side of the case 334 in other implementations (e.g., a longside 377) of the case 334.

FIG. 3E illustrates the device 100 inserted into the case 334. Once thedevice 100 detects that it has been inserted into the case 334 or isotherwise being used with the case 334, (e.g., with near-field wirelesstechniques), the device 100 transitions from displaying the firstgraphical output 337 (e.g., a primary graphical user interface) todisplaying a second graphical output 344. The second graphical output344 is different than the first graphical output 337, and, as shown,includes a graphical object having a size, shape, and position on thedisplay 104 that coordinates with the window 336. Notably, the graphicalobject of the second graphical output 344 may appear out-of-place or mayimpede the display of the main graphical user interface if the device100 were not in the case 334. The second graphical output 344 as shownincludes the current time 376, a message notification icon 338, and acall notification icon 339, though any other types of icons orinformation may be included. The message and call notification icons mayalso include a number of unread or recent messages or calls, thusenabling a user to quickly access information that might be useful tosee without having to remove the device 100 from the case 334.

FIG. 3F illustrates the device 100 inserted into the case 334, with thedevice 100 displaying a third graphical output 345. The third graphicaloutput 345 may include a graphical object that is used in place of thesecond graphical output 344. The particular content, arrangement,appearance, or other property of the graphical object(s) displayed inthe window 336 may be user selectable or configurable. For example, auser of the device 100 may select whether the second or third graphicaloutput 344, 345 is displayed when the device 100 is inserted into thecase 334. The third graphical output 345 may include the current time340, a weather indicator 393 (which may display a graphical depiction ofthe current weather), a day/date indicator 342, and a notificationindicator. The notification indicator may signal that a new notificationis available for the user. The notification may indicate, for example,that an event has occurred on the device 100 (e.g., a voice message hasbeen received, an incoming call was missed, an application has issued anotification or message, a text or email message has been received,etc.). The content of the third graphical output 345 may be configuredto convey information more succinctly and efficiently than aconventional graphical user interface. For example, instead ofindicators that differentiate between different types and amounts ofrecently received messages, the graphical output 345 includes thenotification indicator 341 that relates to multiple different kinds ofmessages. This type of streamlined graphical output may improve thefunctionality of the device 100 by allowing the user to interact withthe device in different ways under different circumstances or use cases.For example, instead of requiring a user to remove the device 100 tocheck for messages or to see the time, the user can simply glance at thedevice 100 through the window 336 to see the desired information.Further, while the same information may also be displayed in a main orprimary user interface, the main or primary interface may show theinformation in smaller or less easily-viewable forms. As such,displaying the information in a more efficient, readable form improvesthe overall usability of the device and the usefulness of the device 100when it is in the case 334.

As noted above, various types of accessories may be configured to usenear-field wireless communication systems to affect the operationalmodes and/or characteristics of devices that are using thoseaccessories. FIGS. 3A-3F, for example, illustrate examples where theaccessory is a protective case for a device. Another type of accessorymay be configured to mount to the device and/or a protective case of thedevice (e.g., on a back surface of the device or case). FIGS. 3G-3Iillustrate one such example accessory.

FIG. 3G depicts a device 346 (which may be in a protective case) and acard wallet accessory 347 that is configured to be removably attached toa surface 351 (e.g., a back surface) of the device 346. The device 346may be or may be an embodiment of the device 100, and may be the same asor similar to the device 100.

The card wallet accessory 347 may include a near-field wirelesscommunication antenna 348 that is detectable by the near-field wirelesscommunication system of the device 346. The card wallet accessory 347may define a first opening 358 that is configured to allow an object(e.g., a bank card 350) to be placed into and removed from an internalcavity of the card wallet accessory 347. The card wallet accessory 347may also define a second opening 349, which may allow the contents ofthe card wallet accessory 347 to be visible to a user and may also allowthe user to touch the contents of the card wallet accessory 347 in orderto slide the contents out of the card wallet accessory 347. The cardwallet accessory 347 may also include magnetic attachment features 359that are configured to removably attach the card wallet accessory 347 tothe device 346 via complementary magnetic attachment features 360 of thedevice 346. The magnetic attachment features 359, 360 may includemagnets, ferromagnetic materials, or the like. In some cases, the device346 may include a metal plate or sheet so that the card wallet accessory347 may be positioned anywhere along the surface 351.

FIG. 3H shows the card wallet accessory 347 removably attached to thesurface 351 of the device 346. As described for other near-fieldwireless enabled accessories, in response to detecting that the cardwallet accessory 347 has been attached to the device 346, the device 346may take an action or change a mode of operation. In the case ofattaching the card wallet accessory 347, the device 346 may log alocation of the device when the card wallet accessory 347 was attached,or display a graphical object (e.g., a notification object that overliesa portion of a graphical user interface) acknowledging that the cardwallet accessory 347 has been attached. In some cases, instead of or inaddition to detecting the card wallet accessory 347, the device 346 maydetect the contents of the card wallet accessory 347. For example, abank card may include a near-field wireless communications antenna thatthe device 346 can detect. In such cases, in response to detecting thatthe card wallet accessory 347 has been attached, the device 346 maydetermine the identify of any near-field wireless enabled cards in thecard wallet accessory 347 and provide an indication to the user of thecontents. As a particular example, a name, icon, or other indicator ofeach card in the card wallet accessory 347 may be displayed on thedevice's display so that a user can easily see what cards are availablejust by viewing the display.

In the case where the device 346 can detect the presence or proximity ofcards or other objects in the card wallet accessory 347, it can alsotake certain actions in response to detecting that a card has beenremoved from the card wallet accessory 347. FIG. 3I illustrates anexample in which a bank card 350 has been removed from the card walletaccessory 347. In response to detecting the removal, the device 346displays one or more graphical objects that are relevant or related tothe removed card 350. For example, the device 346 may display a firstgraphical object 352, which may be an image of the particular bank card350 that was removed. The device 346 may also display a second graphicalobject 353, which may be a recent purchase history associated with thebank card 350. Other types of information and/or graphical objects maybe displayed instead of or in addition to those shown in FIG. 3I.

In other cases, the device 346 may take other actions, initiate otherapplications, or display other types of graphical objects in response todetecting that a card (or the card wallet accessory 347) has beenremoved from the device 346. For example, the device 346 may launch awallet application or a finance application. As another example, thedevice 346 may open an application based on the location of the device346 when the card is removed. More particularly, because the removal ofthe bank card 350 may indicate that the user is about to make apurchase, the device 346 may determine if its location at that timecorresponds to a store and may open an application associated with thatstore. As yet another example, the device 346 may determine if there areany available coupons, deals, rewards, or other offers that areassociated with stores near the user when the card is removed. As yetanother example, the device 346 may associate a geographical locationwith the removal event, as described herein with respect to FIG. 3O-3P.

FIGS. 3J-3L illustrate another example accessory that is configured tomount to a device and/or a protective case of the device (e.g., on aback surface of the device or case). In particular, FIGS. 3J-3L depict adevice 354 (which may be in a protective case) and a battery accessory355 that is configured to be removably attached to a surface 357 (e.g.,a back surface) of the device 354. The device 354 may be or may be anembodiment of the device 100, and may be the same as or similar to thedevice 100.

The battery accessory 355 may include a near-field wirelesscommunication antenna 356 that is detectable by the near-field wirelesscommunication system of the device 354. The battery accessory 355 may beconfigured to charge a battery of the device 354 and/or otherwiseprovide power to the device 354. The battery accessory 355 may providepower to the device 354 via a cable, or it may include a wirelesscharging system comprising an output coil configured to inductivelycouple to a charging coil of the electronic device 354 when the batteryaccessory 355 is removably attached to the device 354.

The battery accessory 355 may also include magnetic attachment features362 that are configured to removably attach the battery accessory 355 tothe device 354 via complementary magnetic attachment features 363 of thedevice 354. The magnetic attachment features 362, 363 may includemagnets, ferromagnetic materials, or the like. The magnetic attachmentfeatures 362, 363 and the charging coils of the battery accessory 355and the device 354 may be embodiments of the corresponding componentsdescribed with respect to FIGS. 2A-2B.

FIG. 3K shows the battery accessory 355 removably attached to thesurface 357 of the device 354. As described for other near-fieldwireless enabled accessories, in response to detecting that the batteryaccessory 355 has been attached to the device 354, the device 354 maytake an action or change a mode of operation. In the case of attachingthe battery accessory 355, the device 354 display a graphical object(e.g., a notification object) providing information about the batteryaccessory 355 and/or its operation with respect to the device 354.

FIG. 3L, for example, illustrates an example graphical object 364 thatmay be displayed by the device 354 in response to the device 354detecting that the battery accessory 355 has been attached to the device354. The graphical object 364 may be displayed as a box that overliesanother graphical user interface, application, or the like, and maydisappear after a certain time or be dismissed by the user. Thegraphical object 364 may display information such as a battery chargelevel of the battery accessory 355 and an estimated time it will takefor the battery accessory 355 to fully charge the device 354 (as shownin FIG. 3L). Other information may also be displayed, such as a name ornickname of the battery, a name of an owner of the battery, a batteryhealth of the battery accessory 355, a predicted charge level of thedevice 354 if the battery accessory 355 remains on the device 354 for acertain period of time (e.g., 1 hour=60% charge; 2 hours=100%), or anyother suitable information.

The device 354 may also initiate actions in response to detecting theremoval of the battery accessory 355. For example, the device 354 maydisplay a graphical object (which may be similar in appearance andfunction to the graphical object 364, and may include a remaining chargeof the battery accessory 355, an amount of charging time that thebattery accessory 355 will require for a full charge. As anotherexample, the device 354 may associate a geographical location with theremoval event, as described herein with respect to FIG. 3O-3P.

FIGS. 3M-3N illustrate an example in which a device detecting aparticular type of case may cause the device to display informationrelevant to that case. For example, as shown in FIGS. 3M-3N, a case 365may include multiple pieces or components that need to be assembled in aparticular way in order to secure the case to the device. Accordingly,the case 365 may include a near-field wireless communication antenna sothat the device can detect when the case 365 is being used and provideassembly instructions and/or other information to the user.

As shown in FIG. 3M, the case 365 includes a back member 367 and aperipheral member 366. The back member 367 is configured to cover andprotect the back of the device 100, while the peripheral member 366protects the sides of the device and holds the back member 367, thedevice 100, and the peripheral member 366 together. The back member 367may include a near-field wireless antenna 368 that is detectable by thedevice 100, as described herein. The peripheral member 366 may have aseam or discontinuity to allow the peripheral member 366 to expand toaccept the device 100 and the back member 367. To secure the case 365,the peripheral member 366 may be closed by closing the seam ordiscontinuity as indicated by arrow 370. The peripheral member 366 mayalso include a latch member 369 that secures the peripheral member 366in the closed configuration.

FIG. 3N illustrates the case 365 in an initial stage of assembly. Inparticular, the device 100 may be placed on the back member 367, whichmay result in the near-field wireless communication antenna 368 of theback member 367 being detected by the near-field wireless communicationsystem of the device 100, which in turn causes a graphical output 371 tobe displayed on the display 104 of the device 100. The graphical output371 may include any suitable text and/or graphical content. In someimplementations, the graphical output 371 includes assembly instructionsfor the case 365. For example, the graphical output 371 may illustratehow to close the seam and secure the latch member 369 to lock theperipheral member 366 around the back member 367 and the device 100. Insome cases, the latch member 369 may include a near-field wirelesscommunication antenna, and the device 100 may be able to detect when thelatch member 369 is in a latched or secured position. In response todetecting that the latch member 369 is in the latched or securedposition, the device 100 may display a graphical object indicating tothe user that the case has been properly and/or completely assembled.

Instead of or in addition to displaying assembly instructions, thedevice 100 may display other graphical objects or graphical userinterfaces, or otherwise change its mode of operation, in response todetecting that it is being used with the case 365. For example, the case365 may be a ruggedized case that is intended for use during outdoorrecreational activities. Accordingly, the device 100 may initialize afitness application, GPS application, or other application that reflectsa probable upcoming activity of the user. As described above, the device100 may use other sensors or information to determine what (if any)applications or operational modes to initiate while the device 100 is inthe case 365. For example, if the device 100 detects that the ruggedizedcase 365 is being attached to the device 100 proximate a trailhead, thedevice 100 may initiate an application associated with hiking (e.g., aGPS application, a fitness tracking application, or the like). If thedevice 100 detects that the ruggedized case 365 is being attached to thedevice 100 proximate a downhill ski facility, the device 100 mayinitiate an application associated with skiing (e.g., a ski trackingapplication, a map of the ski facility, or the like).

As described above with respect to the card wallet accessory and thebattery accessory, a device may take certain actions upon detecting theremoval of an accessory from the device (or upon removal of the devicefrom a case, dock, or any other accessory). For example, the device maylog the location of the device when the accessory was removed. Thisinformation may be helpful for alerting the user to unintendeddetachments of accessories and finding lost accessories. FIGS. 30-3Pdepict a device 100 being used with an accessory 372 (which mayrepresent the card wallet accessory 347, the battery accessory 355, orany other near-field wireless enabled accessory).

FIG. 3O shows the accessory 372 and the device 100 attached. When theaccessory 372 is removed from the device 100 (or the device 100 andaccessory 372 are decoupled), the device 100 may detect the removal bydetecting the absence of the near-field wireless antenna of theaccessory 372. In response to detecting the removal of the accessory372, the device 100 may save information about the removal event. Forexample, the device 100 may determine the location of the device at thetime of the removal of the accessory 372, and a time of the removal ofthe accessory 372. In some cases, the device 100 will display this (orother) information to the user upon removal. For example, as shown inFIG. 3P, the device 100 may display a map 373 with a graphical indicator375 representing the location where the accessory 372 and the device 100were separated. The device 100 may also display textual information 374.In some implementations, the textual information 374 provides textindicating the location (e.g., an address, latitude/longitudecoordinates, or the like), the time of removal, and optionally otherinformation.

The information about the removal of the accessory 372 may be displayedto the user substantially immediately after detecting the removal event,or it may not be displayed and instead be logged for later retrievaland/or viewing by the user. In either case, the information may bestored so that the user can retrieve and view the information as needed.

FIGS. 3A-3P show examples of protective cases and other accessories thatuse a passive antenna to change an operational mode of an electronicdevice when used with the device. Similar principles may apply to deviceholders that are configured to hold or support a device during anactivity. FIG. 4 illustrates two examples of device holders or docksthat may include near-field wireless communication antennas to changethe operational mode of the device 100.

FIG. 4 illustrates the device 100 while displaying a first graphicaluser interface 404, which may be the primary graphical user interface ofthe device 100, such as graphical user interface 128 (FIG. 1B). FIG. 4also shows the device 100 mounted to a dock 400 in a car. The dock 400may include a near-field wireless communication antenna that causes thedevice 100 to switch from displaying the first graphical user interface404 to displaying a second graphical user interface 401 that is tailoredfor use while driving (e.g., the device may cease displaying the firstgraphical user interface and begin displaying the second graphical userinterface). As with the other accessories described herein, thetransition may be automatic and seamless to the user— simply placing thedevice in the dock 400 (e.g., so that the device is positioned on orheld by the dock) may cause the device 100 to transition to thecar-specific graphical user interface.

The graphical user interface 401 may include audio controls that arelarge and easy to see and touch while the user is driving. The graphicaluser interface 401 may also include a map or navigation view. In somecases, the graphical user interface 401 may include large, easy to readicons for various different applications or functions (e.g., radio,telephone, map, messages, etc.). The device 100 may also change otherdevice settings as a result of detecting that it has been mounted to thedock 400. For example, the device 100 may enter a “do not disturb” modethat may reduce the possibility of distraction while driving. This mayturn off message notifications (e.g., text messages, emails, applicationnotifications, etc.) so that the user is not tempted to type responsesor read text-based messages while driving.

FIG. 4 also illustrates the device 100 mounted to a dock 402 on abicycle. The dock 402 may include a near-field wireless communicationantenna that causes the device 100 to cease displaying the firstgraphical user interface 404 and instead display a second graphical userinterface 403 that is tailored for use while cycling. For example, thegraphical user interface 403 is displaying a speed, a heart rate, and adistance travelled. In some cases, placing the device 100 in thebike-mounted dock 402 may cause the device 100 to initiate anapplication, such as an activity tracking application, a biometricmonitoring application (e.g., a heart-rate monitor), a map orpositioning application (e.g., a GPS application), or the like. In somecases, placing the device 100 in the bike-mounted dock 402 (or otherexercise-related dock or accessory, such as a dock on a running strolleror stationary bike, or arm-mounted carrying case) causes the device 100to display an affordance that, when selected by a user, causes thedevice to begin recording a workout associated with the exerciseequipment associated with the dock (e.g., an outdoor bike ride, a run,an indoor bike ride). As another example, placing the device 100 in thebike-mounted dock 402 (or other exercise-related dock or accessory)causes the device 100 to display a list of multiple affordances (e.g.,outdoor bike ride, indoor bike ride, outdoor run, etc.) from which auser may select to initiate a workout recording.

Accordingly, the graphical user interface 403 may be the graphical userinterface of that particular application. In some cases, the graphicaluser interface 403 does not correspond to any single application, butinstead displays outputs from various different applications orfunctions that are being executed by the device. For example, the speedoutput and the distance travelled may be provided by a GPS orcycling-specific application, while the heart rate output is provided bya biometric monitoring function or application. The graphical userinterface 403 may use the data from these applications without executingor displaying the dedicated graphical user interfaces of thoseapplications.

While the graphical user interface 403 is shown as having only outputs,it may also or instead include selectable inputs, such as audio controlsthat are large and easy to see and touch while the user is riding, largeicons for various different applications or functions (e.g., radio,telephone, map, messages, etc.). The device 100 may also change otherdevice settings as a result of detecting that it has been mounted to thedock 402. For example, the device 100 may enter a “do not disturb” modethat may reduce the possibility of distraction while cycling. This mayturn off (or mute) message notifications (e.g., text messages, emails,application notifications, etc.) so that the user is not tempted to typeresponses or read text-based messages while cycling. In someimplementations, when the device 100 is being used with other docksand/or accessories, such as home-based docks, protective cases, chargingdocks, wallet accessories, auxiliary batter accessories, etc., messagenotifications are not turned off or muted (e.g., they are displayed orotherwise provided to the user).

The device 100 may be mounted to other types of docks. For example, thedevice 100 may be mounted to docks that are integrated with or otherwiseassociated with exercise equipment such as stationary bicycles, rowingmachines, elliptical machines, stair-climbing machines, or the like.When mounted to exercise equipment, the device 100 may detect the typeof exercise equipment it is mounted to and initiate a coachingapplication or service that is relevant to that particular equipment.The device 100 may also use additional information to determine whattype of coaching application or service to use, or whether to display auser interface that does not include a coaching service or interface.For example, the device 100 may use the device's location to determineif it is mounted to the user's home stationary bike or a stationary bikeat a fitness studio. If it is mounted to the home stationary bike, thedevice 100 may initiate a coaching application or service, and if it ismounted to a bike at a fitness studio, the device may not initiate thecoaching application (reflecting the fact that the fitness studio mayhave live coaches, for example).

The accessories shown in FIGS. 3A-4 may have features and physicalcharacteristics that make them suited to certain uses. For example, aruggedized case may be targeted for rough work environments, and a sportcase may have straps so the case can be worn during workouts. Whilethese accessories may cause a device to change its operation usingnear-field wireless communication systems, they do not communicate withor interact with the device 100 in other ways. However, accessories thatuse near-field wireless communication systems may also have othercomponents, systems, or mechanisms that interact or communicate with thedevice 100 to expand the functionality of the accessory and/or thedevice 100.

FIG. 5 illustrates two examples of protective cases that use near-fieldwireless communications to cause the device 100 to change its mode ofoperation and also include input systems that wirelessly communicatewith the device 100 and provide auxiliary inputs for a user. Forexample, FIG. 5 shows the device 100 not attached to an accessory orinserted in a case, and displaying a first graphical user interface 501,which may be the primary graphical user interface of the device 100,such as graphical user interface 128 (FIG. 1B). FIG. 5 also shows thedevice 100 after it has been inserted into a camera case 500. Similar tothe other protective cases described herein, the camera case 500 mayinclude a near-field wireless communication antenna that causes thedevice 100 to cease displaying its first graphical user interface andreplace it with a second graphical user interface. In this case, becausethe case 500 is configured to facilitate the use of the device's camerafunctions, the second graphical user interface may be an image-captureinterface 508. The image-capture interface 508 may include a preview ofthe scene at which the device's camera is aimed, as well as otherselectable regions or input areas for controlling aspects of the camerafunctions (e.g., flash settings, aperture, shutter speed, white balance,image-capture type (e.g., video mode, still image mode, slow-motionmode), self-timer settings, shutter button, front/back camera selector,or the like. The device 100 may transition from the first graphical userinterface 501 to the media-capture interface 508 (e.g., a still imagecapture user interface or a video capture user interface) when thedevice 100 is inserted into the camera case 500, or if the device'sdisplay is off when the device 100 is inserted into the camera case 500,the display may automatically turn on and immediately display theimage-capture interface 508.

The camera case 500 may also include auxiliary input systems, such asbuttons 502, that are configured to control image-capture functions ofthe device 100. For example, one of the buttons 502 may act as a shutterbutton to capture an image or begin or end a video recording. As anotherexample, the buttons 502 may control zoom functions, aperture settings,shutter speed, or any other image-capture functions. The camera case 500may also have a button mechanism 506 that allows a user to actuate abutton of the device 100 itself. For example, the button mechanism 506may include a movable button member (or membrane or material) thattransfers force from a user's finger to the button 108 of the device 100(FIG. 1A) to mechanically actuate the button 108. In some cases, whenthe device 100 is inserted into the camera case 500, the detection ofthe near-field wireless communication antenna of the camera case 500causes the device 100 to re-map the input from the button 108 from afirst function, such as locking the phone and/or deactivating thedisplay, to a second function, such as a shutter button. This re-mappingmay occur whenever the device 100 is in the camera case 500 and thedevice 100 is in an image-capture mode. That is, a user may leave animage-capture mode (and thus leave the image-capture interface 508) anduse the device 100 in other modes (e.g., using the primary graphicaluser interface 501) while the device 100 remains in the camera case 500.Under such circumstances, the device may revert the button 108 to adefault function, and may re-map the buttons 502 to other functions.When the user re-initializes the image-capture interface, the device 100may once again use the buttons 108, 502 to control aspects of theimage-capture functions of the device 100.

Actuation signals from the buttons 502 may be detected by the device 100in various ways. In some cases, the buttons 502 use near-field wirelesscommunication techniques to provide inputs to the device 100. Forexample, the buttons 502 (or any other type of input system) may includean actuation member configured to be actuated by a user. The actuationmember may be any component that is actuated by a user, such as rigidbutton member, a membrane, or the like. The buttons 502 may furtherinclude a passive antenna, such as a near-field wireless communicationantenna. When the actuation member is actuated by the user (e.g.,pressed), the buttons 502 may cause the near-field wirelesscommunication antenna to become detectable by the electronic device. Forexample, when the buttons 502 are in an unactuated state, the near-fieldwireless communication antenna may be in a state or configuration thatcauses the antenna to not detectable by the device 100. This may becaused by the antenna being electrically decoupled from other circuitelements, grounded, electrically coupled to other circuit elements, orotherwise put into a state where the near-field wireless communicationsystem of the device 100 does not (and/or cannot) detect the antenna. Inresponse to the actuation member being actuated by the user, the passiveantenna may become detectable by the electronic device. Moreparticularly, the user actuating the actuation member (e.g., by pressingit with a finger or other object) may change the electricalconfiguration of the antenna and/or associated circuitry in a mannerthat makes the antenna detectable by the device. For example, pressingthe actuation member may cause an electrical contact to close, therebyconnecting the antenna to a circuit element (e.g., a capacitor, aninductor, a resistor, etc.) to make the antenna detectable by thenear-field wireless communication system of the device 100. In anotherexample, pressing the actuation member may cause an electrical contactto open, thereby decoupling the antenna to an electrical ground. Othertechniques may also be used to cause the antenna to switch between adetectable state and an undetectable state. Further, other techniquesmay be used to wirelessly communicate actuation signals from the buttons502 to the device 100, such as other wireless communication protocols(e.g., Bluetooth, WIFI), acoustic signals (e.g., audible, ultrasonic),light, or the like.

The device 100 may be configured to execute an operation in response todetecting the passive antenna with the device's near-field wirelesscommunication system. For example, when the user presses or actuates oneof the buttons 502, the antenna associated with the button may bedetected by the near-field wireless communication system of the device100. The antenna may communicate some information to the device 100 thatcauses the device to perform a function such as capture an image, zoomin or out on a scene or subject, change a camera setting (e.g.,aperture, shutter speed), or the like. The information communicated tothe device 100 by the antenna may be a command to execute a particularfunction, an identifier that the device 100 uses to lookup an associatedfunction or command, or any other suitable information.

Because the camera case 500 may include auxiliary inputs (or mayotherwise cause a user to operate the camera function differently thanwhen the device 100 is not in the camera case 500), the image-captureinterface 508 may be different than an image-capture interface that isdisplayed when the device 100 is not used with the camera case 500. Forexample, a default image-capture interface for use without the cameracase 500 may include selectable shutter button objects and other settingcontrols on the display of the device. Because the camera case 500 mayinclude physical buttons to control these functions, in someimplementations separate display-based controls for the functions areomitted from the image-capture interface 508 (while in otherimplementations, display-based controls for the functions are displayedon the image-capture interface 508, such that the user can use thedisplay-based controls and/or the physical buttons. The image-captureinterface 508 may differ from a default image-capture interface in otherways as well. The image capture interface 508 is shown displayingshapes, though the shapes represent a live preview of the camera (e.g.,the image the camera will capture when an image capture command (e.g.,shutter button) is received).

Gaming case 510 is another example case that may use a near-fieldwireless communication antenna to cause a device to change to anoperating mode that is contextually relevant to the intended use ofcase, and also use near-field wireless communication systems to provideauxiliary inputs that are contextually relevant to the intended use ofthe case. For example, the gaming case 510 may have a near-fieldwireless communication antenna that causes the device 100 to enter agaming mode, which may include transitioning from a first graphical userinterface to a gaming graphical user interface 516. In someimplementations, the gaming graphical user interface 516 is a selectionscreen of gaming applications (represented by the application icons withthe triangle, circle, and square shapes) that a user may select, thoughthe gaming graphical user interface 516 may be any other type ofinterface. For example, attaching the gaming case 510 to the device 100may cause the device 100 to launch a single gaming application (whichmay be selected by the user), thereby causing that game's dedicatedgraphical user interface to appear.

Like the camera case 500, the gaming case 510 may include auxiliaryinputs 512, 514 that use near-field wireless communication antennas tosignal input events to the device 100. In some implementations, theauxiliary input 512 is a directional pad (e.g., a generally plus-shapedinput member that can be used to provide directional inputs), ajoystick, an analog controller, or the like. In some implementations,the auxiliary inputs 514 are buttons. The auxiliary inputs 512, 514 mayuse the same or similar techniques as the buttons 502 to activate and/ordeactivate near-field wireless communication antennas.

The device 100 may be configured to dynamically re-map the auxiliaryinputs 512, 514 based on the game, application, operating mode, orgraphical user interface that is active on the device 100. For example,when the user places the device 100 into the gaming case 510, the device100 may enter a gaming mode or graphical user interface, and theauxiliary inputs 512, 514 may be mapped to gaming inputs (e.g., tocontrol a character or other aspect of a game). If the user exits thegaming mode while the device 100 is still in the gaming case 510, theauxiliary inputs 512, 514 may be re-mapped to other functions. Forexample, the directional pad 512 may control the position of a cursor onthe display or change a selected object, and the buttons 514 may selectitems, launch applications, switch the device between differentapplications or user interfaces, or the like. When the user returns tothe gaming mode, the auxiliary inputs 512, 514 may be re-mapped to thegaming functions.

While several examples of protective cases are described above, theseare merely some of the numerous types of accessories, and associatedchanges to the operating mode of the device, that may use near-fieldwireless communication techniques to automatically customize theoperation of a device. As one example of another accessory, a protectivecase may include a keyboard that wirelessly communicates with thedevice. When the device 100 is positioned in the case with the keyboard,the device 100 may change a setting so that an on-screen keyboard is notdisplayed when text input fields are selected or available, and so thatinputs from the case's keyboard are used for text input. The device 100may change its mode of operation in other ways, including changing anauto-correct model and/or algorithm (e.g., from one that is tailored totouch-screen based inputs to one that is tailored for physical keyinputs from the keyboard), changing sound and/or tactile outputsassociated with key presses, and the like. The device 100 may alsoinitiate a pairing sequence or otherwise initialize wirelesscommunication with the keyboard upon detecting the keyboard case. Thekeyboard may communicate with the device using any suitablecommunication technique or protocol, including wireless communicationssuch as WIFI, Bluetooth, near-field wireless communications, or thelike. In some implementations, the keyboard communicates with the devicevia a direct physical connection (e.g., a wired connection). In somecases, the keyboard may be associated with a keyboard dock orstand-alone keyboard instead of a protective case. In such cases, thenear-field wireless communication system of the device 100 may detectwhen the device 100 is docked on the keyboard or otherwise in proximityto the keyboard.

Another example protective case may include a battery that may rechargethe device 100 (either via physical connectors or wirelessly) when thedevice 100 is in the case. Upon the device 100 being inserted into thecase or otherwise used with the battery, the device 100 may display anotification indicating that a battery has been attached and optionallyproviding selectable inputs to control aspects of a charging function(as shown with respect to FIG. 2A). The device 100 may also record thelocation of the device 100 when the battery-enabled protective case wasattached to or removed from the device 100.

Accessories need not be protective cases that enclose or cover thedevice 100. For example, a card-holder or wallet-type accessory may beconfigured to attach to a device (or to a protective case), and thedevice 100 may use its near-field wireless communication system todetect when the card-holder accessory is attached to and removed fromthe device. The device 100 may customize a graphical user interface inresponse to detecting that the card-holder accessory has been attached(e.g., changing a background color or image of a primary graphical userinterface to match a color of the accessory, or changing a color schemeor background of a graphical user interface of a digital walletapplication to match the card-holder accessory). The device 100 may alsouse the near-field wireless communication system to help a user identifywhen and where the card-holder accessory is removed from the device. Forexample, upon the device 100 detecting that the card-holder accessoryhas been removed from the device 100, the device 100 may record thecurrent time and the location of the device 100 (e.g., from a GPS orother positioning system). This information may then be provided to auser to help the user locate the card-holder accessory or at least knowwhen and where the card-holder accessory was lost or removed. Forexample, a notification may be provided on the display of the devicethat shows the time and location (e.g., on a map) when the accessory wasremoved from the device 100.

Some accessories, such as some of the cases described above, may beconfigured to cause the device 100 to enter a particular operating modeor initiate a particular application that is tailored for use with thatcase. For example, the camera case 500 may cause the device to initiatea camera application. In some cases, a user may be able to customize howa device behaves, such as what is presented on its graphical userinterface, when it is used with different accessories. For example, thedevice 100 may allow the user to create multiple different auxiliarygraphical user interfaces that each include desired interfacecomponents. The user can also associate the auxiliary graphical userinterfaces with respective accessories. For example, the user can createone auxiliary graphical user interface that is activated (e.g.,displayed instead of a primary graphical user interface) when the deviceis placed on a dock in a bedroom, and a second, different graphical userinterface that is activated when the device is placed on a dock in akitchen. In some cases, the user can create numerous different auxiliarygraphical user interfaces for numerous different use cases andaccessories.

The auxiliary graphical user interfaces may be created by allowing auser to select from a group of candidate graphical objects. FIG. 6 , forexample, illustrates an example group of candidate graphical objects,including an audio control object 600, a home automation object 602, arecipe object 604, a timer object 606, a calendar object 608, a channelguide and selection object 610, a clock object 612, a weather object614, and a news-feed object 616. In order to create an auxiliarygraphical user interface, the user may select graphical objects from thegroup of candidate graphical objects, associate them with particularlocations on the display 104 of the device 100 (e.g., defining auser-defined arrangement), and associate the auxiliary graphical userinterface with a particular accessory. The graphical objects may haveinput objects, output objects, or both. Notably, the user may definenumerous auxiliary graphical user interfaces each with different objectsor different combinations of objects (or even with the same objects in adifferent user-defined arrangement). For example, one auxiliarygraphical user interface may include the audio control object, whileanother may lack the audio control object. By providing suchflexibility, users can produce highly customized and relevant auxiliaryuser interfaces for use with numerous different docks and accessories.

In some implementations, auxiliary graphical user interfaces areassociated with specific docks or other accessories. For example, insome implementations, a user creates an auxiliary graphical userinterface (e.g., by selecting a set of graphical objects from thecandidate graphical objects), and associates the created auxiliarygraphical user interface with a dock (e.g., by creating the auxiliarygraphical user interface while the device is on the dock, by placing thedevice on the dock after creating the auxiliary graphical userinterface, by manually associating the dock with the created auxiliarygraphical user interface, or the like). Thereafter, when the device isplaced on the dock, the user-created auxiliary graphical user interfaceis displayed. The same process may be used to create other customizedauxiliary graphical user interfaces that are associated with otherdocks.

The audio control object 600 may include audio control input objects(“audio control inputs”) for controlling audio playback functions of thedevice 100 or any other device that the device 100 can control. Forexample, the audio control inputs of the audio control object 600 may beconfigured to control audio of a network-connected audio system that thedevice 100 can control using network communications. The audio controlobject 600 may also have output objects, such as an indicator of thecurrently played or queued media, album art, or the like.

The home automation object 602 may include input objects that allow theuser to control network-connected home automation systems, such asalarms, lighting, audio systems, HVAC systems, and the like. The homeautomation object 602 may also include output objects that indicate thestate of interconnected systems, such as the lights, door sensors,window sensors, and the like. As noted above, in some implementations, adock can be associated with a particular virtual room or environment ina home automation platform. Accordingly, when the device is placed on adock associated with a particular virtual room or environment, the homeautomation object 602 may display controls for devices that are alsoassociated with the particular room or environment. Thus, for example, ahome automation object 602 that is displayed when the device is placedon a dock associated with and/or assigned to a “dining room” environmentin the home automation platform can display controls for operating thelights of the dining room, while a home automation object 602 that isdisplayed when the device is placed on a dock associated with and/orassigned to a “living room” environment in the home automation platformcan display controls for operating the lights in the living room, aswell as a television and an audio system. Accordingly, the user need notmanually select individual devices (e.g., a television, a set of lights,etc.) to associate with the home automation object (though in somecases, that is also an option). In some implementations, a homeautomation object in an auxiliary graphical user interface includesdifferent controls based on the time of day. For example, a homeautomation object in an auxiliary graphical user interface for a bedroomdock may display, when the device is placed on the dock during the day,controls for an audio system, and, when the device is placed on the dockduring the evening, controls for bedroom lights and a home alarm system.

The recipe object 604 may display cooking recipes or recipe lists. Therecipe object 604 may also provide a search interface for searching forrecipes. The timer object 606 may provide inputs for setting a timer andselecting timer settings (e.g., alert tones, volume, etc.), and maydisplay timer progress. The calendar object 608 may show a snapshot of auser's calendar items. The channel guide and selection object 610 maydisplay a list of channels, shows, show times, or other televisionprogram information. The channel guide and selection object 610 may alsoprovide input objects for controlling a television, DVR, DVD player, orthe like. The clock object 612 may display the current time. The weatherobject 614 may display current weather conditions and/or weatherforecasts. The news-feed object 616 may display news headlines orarticles.

The foregoing represents only some of the possible graphical objectsthat may be provided to a user to create auxiliary graphical userinterfaces. In some cases, more, fewer, or additional graphical objectsmay be provided as well. The graphical objects may be associated with oruse functions of other applications that are executed by the device 100.For example, a timer application (which may have its own separategraphical user interface) may provide timing functions for the timerobject 606. In some cases, the functions of multiple differentapplications are included in a single graphical object. For example, thehome automation graphical object 602 may use functions provided by alighting application (on the device 100) to control lights, andfunctions of a separate thermostat application (on the device 100) tocontrol the HVAC system.

Associating the auxiliary graphical user interface with a particularaccessory may include associating the auxiliary graphical user interfacewith an identifier of a near-field wireless communication antenna of theaccessory. For example, when a device is placed on or used with anaccessory for the first time, the device may prompt the user to createan auxiliary graphical user interface for use with that accessory. Thedevice may then store the association between the auxiliary graphicaluser interface and the accessory so that when the device detects theaccessory in the future (e.g., using the near-field wirelesscommunications described herein), the device will transition fromdisplaying a first graphical user interface (e.g., whatever graphicaluser interface is active at that time) to displaying the auxiliarygraphical user interface associated with that accessory.

In some cases, instead of an auxiliary graphical user interface thatincludes a set of user-selected graphical objects, a user may associatea particular accessory or dock with a particular application. Forexample, a device may include a dedicated application for a socialnetwork, a telephone, a video phone, a music player, or the like. Theuser may select any given application to be executed and/or initializedwhen the device is placed in a particular dock. Thus, as one example,the user may associate a video phone application with a dock that sitson the user's desk. Whenever the user places the device in that dock,the video phone application may be initialized (including, for example,causing the device to display the graphical user interface of the videophone application). In some cases, a phone or video phone applicationmay be configured to initiate a call or an audio and/or video streamwith another device in response to the device being placed in aparticular dock. For example, when the user places the device in a dockat the user's work desk, a live video stream of the user's home securitycamera (or any other electronic device) may be displayed on the device.As another example, when the user places the device on a dock at theuser's home desk, a video call with another person may be initiated. Asdescribed above, in some implementations, the particular application(s),control(s), and/or graphical object(s) that are executed and/ordisplayed in response to the device being placed on or used inconjunction with a dock or other accessory are based on an assignment ofthe dock or other accessory to a room in a home automation platform.Thus, for example, when a device detects that it is placed on a dockthat is associated with or assigned to an “office” environment in a homeautomation platform, the device can execute an application or showcontrols that are also associated with the “office” environment. In somecases, multiple docks or accessories may be associated with the sameroom or environment in a home automation platform. In such cases, thedifferent docks, even when associated with the same room or environment,may cause a device to execute or display different application(s),control(s), and/or graphical object(s). In some implementations, theparticular application(s), control(s), and/or graphical object(s) thatare displayed and/or executed are based on a property or type of dock(e.g., an alarm clock dock in a bedroom may cause alarm controls to bedisplayed, while a charging dock in the bedroom may cause lighting andaudio controls to be displayed), or based on a user selection (e.g., auser can specify that a first bedroom dock will cause a first set ofapplication(s), control(s), and/or graphical object(s) to be displayedand/or executed, and a second bedroom dock will cause a second set ofapplication(s), control(s), and/or graphical object(s) to be displayedand/or executed).

In some cases, multiple individuals may configure their devices anddocks to initiate a video call or video conference whenever two or moreof the devices are placed on particular docks. For example, two usersmay configure their devices so that if one user places his or her deviceon a particular dock while the other user's device is also on a dock, avideo call (e.g., a live or streaming video feed) is automaticallyinitiated (e.g., without further user input). The video call may beterminated automatically upon either of the devices being removed fromtheir respective docks. This may provide an easy and efficient way forfamily, friends, and coworkers to communicate with one another. Whilethe foregoing example describes a two-person communication link, asimilar technique may be used for more than two users. For example, agroup of coworkers may each configure their device to initiate a videoconference when their device is placed on a dock at their work place. Inthis way, they may be able to instantly collaborate with anyone else intheir company or work group that is also available at that time. Theuser may simply remove their phone from the dock when they no longerneed or want to communicate with that group. A user may even configuretheir device to join a different video conference when it is placed on adifferent dock. Accordingly, a user can communicate with differentgroups simply by moving their device to a different dock. While theforegoing examples are described primarily with respect to videoconferences or video calls that are initiated by placing a device on adocking accessory, the same principles may be applied to audio-onlycommunications (instead of video) and other types of accessories such asprotective cases, charging docks, charging mats, vehicle-mounted docksor holders, or the like.

FIG. 7 illustrates how various different auxiliary graphical userinterfaces may be displayed on the device 100 based on what accessory ordock the device 100 is placed on. Each dock shown in FIG. 7 may includea near-field wireless communication antenna that allows the device 100to detect when it has been placed on the support structure. Further,each dock may include a support structure that is configured to hold thedevice in a viewable orientation when the dock is on a surface of anobject (e.g., structure 701 of the dock 700). The surface of an objectmay correspond, for example, to a surface of a table, counter, desk,nightstand, dresser, or any other suitable object. In this way thedevice can be viewed and interacted with, including allowing the user totouch the device to provide inputs (by pressing buttons, providing touchor stylus inputs on a touch sensitive surface, or the like). Further,the support structure may allow a user to simply place the device ontothe support structure and remove it from the support structure (andconsequently cause it to initiate a different operating mode and/orgraphical user interface) without additional steps such ascommunicatively pairing the devices, mechanically securing the device toor in the dock, aligning and coupling electrical connectors, or thelike.

Returning to FIG. 7 , when the device 100 is placed on the first dock700, the device 100 may detect, with its near-field wirelesscommunication system, the antenna of the first dock 700 and therebydetermine that it is in proximity to (e.g., placed on) the first dock700. The device 100 may then determine what mode of operation it shouldoperate in based on its proximity to the first dock 700 (e.g., whatauxiliary graphical user interface to display) and begin operating inthe mode of operation that corresponds to the first dock 700 (e.g., itmay display the graphical user interface that has been associated withthat dock). In the example shown in FIG. 7 , the device 100 may displaya first auxiliary graphical user interface 710, which may include achannel guide and selection object (e.g., allowing a user to view andselect channels to view on a television) and a home automation object(e.g., allowing a user to control home automation systems such aslights, security systems, door locks, thermostats, etc.). Thesegraphical objects which may have been selected by the user to bedisplayed when the device 100 is in this particular dock. For example,the first dock 700 may be located in a user's living room or recreationroom where television channel selection and home automation controls areparticularly useful to the user. Of course, because a user can customizethe graphical user interface for any dock in any location, the contentsof the first auxiliary graphical user interface 710 are merely examplesand may be customized by a user to fit the user's particular needs for aparticular dock location.

The first auxiliary graphical user interface 710 may be displayed whenthe device 100 is placed on the dock 700 regardless of what wasdisplayed immediately prior. For example, if the device 100 is notdisplaying anything (e.g., the display 104 is blank), the display 104may turn on and immediately display the first auxiliary graphical userinterface 710. If the device 100 is currently displaying a primarygraphical user interface (e.g., the primary graphical user interface128, FIG. 1B), the device may cease displaying the primary graphicaluser interface and instead display the first auxiliary graphical userinterface 710.

When the device 100 is placed in a second dock 702, the device 100 maydetect, with its near-field wireless communication system, the antennaof the second dock 702 and thereby determine that it is in proximity to(e.g., placed on) the second dock 702. The device 100 may then determinewhat mode of operation it should operate in based on its proximity tothe second dock 702 (e.g., what auxiliary graphical user interface todisplay) and begin operating in the mode of operation that correspondsto the second dock 702 (e.g., it may display the graphical userinterface that has been associated with that dock). In the example shownin FIG. 7 , the device 100 may display a second auxiliary graphical userinterface 712, which may correspond to a live video stream captured by aremote electronic device and sent to the device 100. More particularly,when the device 100 is placed on the second dock 702, a live video linkwith another device may be automatically initiated. The live video linkmay be with another similar device (e.g., a mobile phone, tabletcomputer, laptop computer) that allows two-way audio and videocommunications, or with a camera such as a security camera or webcam.Accordingly, the second auxiliary graphical user interface 712 maycorrespond to a video feed from another camera. As another example,instead of automatically initiating the live video link, placing thedevice 100 on the second dock 702 may cause the device 100 to display alist of contacts that a user can select to initiate a live video oraudio feed with the selected contact. The device 100 may also activate amicrophone or voice recognition scheme to accept a spoken command (e.g.,“call my mother”). As noted above, the second auxiliary graphical userinterface 712 may be displayed when the device 100 is placed on thesecond dock 702 regardless of what was displayed on the device 100immediately prior. For example, the device 100 may transition from ablank screen to the second auxiliary graphical user interface 712 orfrom another graphical user interface (e.g., a primary graphical userinterface) to the second auxiliary graphical user interface 712.

When the device 100 is placed in a third dock 704, the device 100 maydetect, with its near-field wireless communication system, the antennaof the third dock 704 and thereby determine that it is in proximity to(e.g., placed on) the third dock 704. The device 100 may then determinewhat mode of operation it should operate in based on its proximity tothe third dock 704 (e.g., what auxiliary graphical user interface todisplay) and begin operating in the mode of operation that correspondsto the third dock 704 (e.g., it may display the graphical user interfacethat has been associated with that dock). In the example shown in FIG. 7, the device 100 may display a third auxiliary graphical user interface714, which may include graphical objects relevant to a kitchenenvironment. For example, in some implementations, the third auxiliarygraphical user interface 714 includes a recipe object that may allow auser to search for recipes, select from saved recipes, and read recipes.The third auxiliary graphical user interface 714 may also include atimer object, and/or a measurement conversion object.

Activation of the third auxiliary graphical user interface 714 may alsoconfigure the device to respond to spoken instructions (e.g., to scrollthe recipe or change between recipes, to control the timers, etc.) sothat the user does not need to touch to the device 100 to manipulate theuser interface during cooking, which may be unsanitary and may damagethe device 100. Further, an automatic display shutoff may be disabled sothat the display (and thus the recipe, timers, etc.) do not disappearwithout warning. Of course, other user-selected graphical objects may beused instead of or in addition to those shown in the third auxiliarygraphical user interface 714.

In some cases, docks that include support structures to hold the devicein a viewable orientation may also include input systems that areconfigured to wirelessly communicate with the device in response to theinput system being actuated by a user when the electronic device ispositioned on the support structure. For example, FIG. 7 shows anexample alarm clock dock 706 that includes input systems such as buttons720. The buttons 720 may be similar to those described with respect toFIG. 5 . For example, actuation signals from the buttons 720 may bedetected by the device 100 in various ways. In some cases, the buttons720 use near-field wireless communication techniques to provide inputsto the device 100. For example, the buttons 720 (or any other type ofinput system) may include an actuation member configured to be actuatedby a user, as well as a passive antenna, such as a near-field wirelesscommunication antenna. When the actuation member is actuated by the user(e.g., pressed), the buttons 720 may cause the near-field wirelesscommunication antenna to become detectable by the electronic device. Forexample, when the buttons 720 are in an unactuated state, the near-fieldwireless communication antenna may be in a state or configuration thatis not detectable by the device 100. This may be caused by the antennabeing electrically decoupled from other circuit elements, grounded,electrically coupled to other circuit elements, or otherwise put into astate where the near-field wireless communication system of the device100 does not detect the antenna. In response to the actuation memberbeing actuated by the user, the passive antenna may become detectable bythe electronic device. (Other techniques may be used to wirelesslycommunicate actuation signals from the buttons 502 to the device 100,such as other wireless communication protocols (e.g., Bluetooth, WIFI),acoustic signals (e.g., audible, ultrasonic), light, or the like.)

As with the other docks shown in FIG. 7 , placing the device 100 on thedock 706 may cause the device 100 to display a fourth auxiliarygraphical user interface 716. In some implementations, the fourthauxiliary graphical user interface 716 includes clock and/or alarm clockgraphical objects. Accordingly, the dock 706 may be suited for placementin a user's bedroom. The buttons 720 may be configured to control orchange settings of the clock and/or alarm clock graphical objects, suchas setting alarm times, snoozing an alarm, changing the displaybrightness (e.g., temporarily activating the display so that a user cansee the time during the night), or the like. This may improve theexperience of using the alarm functions of the device 100 by eliminatingthe need for a user to look at the display of the device to locate atouch-sensitive snooze button or otherwise control alarm functions.

In addition to transitioning to the fourth auxiliary graphical userinterface 716 in response to being placed on the dock 706, the device100 may also change other device settings. For example, where the dock706 is in a bedroom and being used as an alarm clock, the device mayalso change notification settings (e.g., turning off audible, visible,and/or tactile notifications of messages, events, etc.), change displaysettings (e.g., display brightness, display color content, etc.). Otherdevice customizations are also possible upon the device 100 detectingthat it is on the dock 706.

While FIG. 7 shows several example docks and associated auxiliary userinterfaces, other types of docks are also possible, including dockshaving different form factors, different targeted uses and/or locations,different arrangements and types of auxiliary input systems, and thelike. For example, a dock may include speakers (like the dock 118, FIG.1A) and may cause the device 100 to transition to an auxiliary graphicaluser interface that includes music or audio-control objects. As anotherexample, a dock without speakers may cause the device 100 to transitionto an auxiliary graphical user interface that includes music oraudio-control objects and also configures the device to control orconnect with a wireless speaker system.

Another example dock may cause the device 100 to transition to anauxiliary graphical user interface that is configured as a shared familydevice. This may include displaying a shared (e.g., among a family)calendar, task list, reminder list, or the like, as well as objects forcontrolling home functions such as security systems, a thermostat,lighting, music, or the like. In some implementations, sharedinformation (e.g., among a family) corresponds to information that isshared between accounts that are linked to a shared family account andshare access to information and/or content (e.g., a calendar, photos,contacts, etc.) and/or payment methods. In addition to transitioning tothe auxiliary graphical user interface, the device may also changedevice settings by restricting access to a single user's personalcontent (e.g., messaging applications and functions, etc.), changingnotification settings (e.g., turning off notifications or removingvisible message previews), and the like.

Another example dock may cause the device 100 to transition to anauxiliary graphical user interface that is configured as a voice-baseddigital assistant interface. This may include dynamically displayingtranscriptions of voice input, displaying content or graphical objectsrelated to voice-based commands issued to the device 100, or the like. Adock configured to customize the device for use as a digital assistantmay also include microphones and/or speakers that can communicate withthe device 100 to enhance the device's audio capabilities.

Another example dock may cause the device 100 to transition to anauxiliary graphical user interface that is configured to control anappliance that is wirelessly coupled to the device 100 or otherwiseconfigured to receive and/or respond to commands from the device 100.For example, an auxiliary graphical user interface for controlling awashing machine may include control objects tailored to the washingmachine's functions (e.g., water temperature, spin cycle level, cycletime, soil level). As another example, a user interface that isconfigured to control a coffee maker may include control objectstailored to the coffee maker's functions (e.g., brew start time, coffeestrength, grind size, water temperature). Of course, auxiliary userinterfaces may be tailored for use with other appliances and devices aswell.

Docks may also be provided at public places, businesses, or otherlocations where they may be used by many different users. Such docks maycause devices to transition to auxiliary graphical user interfaces thatare relevant to their locations and/or environments. For example, arestaurant may provide docks at their tables that cause devices todisplay a menu and/or ordering interface when the devices are placed onthe docks. As another example, an airport may have docks at each gatethat cause devices to display flight information for that gate. Asanother example, parks may have docks at points of interest that causedevices to display information or interactive applications related tothose points of interest. Shared docks such as those described above(and indeed any dock described herein) may also include wirelesscharging systems as described above with respect to FIGS. 2A-2B.

As described above, auxiliary user interfaces may be customized by auser and associated with a particular dock. In some cases, docks may beconfigured to trigger a pre-populated auxiliary graphical userinterface. For example, a dock may be sold as a “kitchen” dock, and thedock and/or devices that are usable with the dock may be configured totrigger an auxiliary graphical user interface that includes a recipeobject and a timer object. The user may use the default auxiliarygraphical user interface, or modify and/or change the auxiliarygraphical user interface in any manner (e.g., with different cooking orkitchen-relevant objects, or so that the dock can be used in an entirelydifferent context such as on the user's nightstand). Other types of“default” docks may also be provided and may trigger similarly tailoredauxiliary graphical user interfaces. For example, a “bedroom” dock may,by default, trigger an interface with an alarm clock object, and a“living room” dock may, by default, trigger a television control object.Of course, these default auxiliary graphical user interfaces may bereplaced or modified by the user using the modular user interface schemedescribed herein.

While the docks, cases, and other accessories described herein may causethe device to transition from one mode of operation to another(including, for example, transitioning from one graphical user interfaceto another, different graphical user interface), users may be able toselectively return to a previous or a different mode of operation (andassociated graphical user interface) while the device is stillassociated with an accessory. For example, when a device is placed onkitchen dock, thus triggering the transition to a cooking-based userinterface, the user may control the device to leave the cooking-baseduser interface and instead return to a primary graphical user interfacewhile the device remains on the dock. As another example, the user maycontrol the device to leave the cooking-based user interface and insteadinitiate a music-playback interface. A user may also be able to selectwhether or not a particular graphical user interface may be freelychanged. For example, if a user places a device in a child-proof case,they may not want the child to be able to freely return to the primaryuser interface. Accordingly, users may be able to select what auxiliarygraphical user interfaces (if any) may be freely available once a deviceis used with a particular accessory. A password or other authenticationmay be required in order to transition between auxiliary userinterfaces.

In some cases, the device 100 transitions from an auxiliary graphicaluser interface to a primary graphical user interface when the device 100is removed from a dock. For example, the near-field wirelesscommunication system of the device 100 may determine that the device isno longer in proximity to the dock based on ceasing to detect thenear-field wireless antenna of the dock. Upon ceasing to detect thenear-field wireless antenna of the dock, the device 100 may ceasedisplaying the auxiliary graphical user interface (or any othergraphical user interface associated with that dock) and begin displayingthe primary graphical user interface.

FIG. 8 depicts an example schematic diagram of an electronic device 800.By way of example, the device 800 of FIG. 8 may correspond to theelectronic device 100 shown in FIGS. 1A-7 (or any other electronicdevice described herein). To the extent that multiple functionalities,operations, and structures are disclosed as being part of, incorporatedinto, or performed by the device 800, it should be understood thatvarious embodiments may omit any or all such described functionalities,operations, and structures. Thus, different embodiments of the device800 may have some, none, or all of the various capabilities,apparatuses, physical features, modes, and operational parametersdiscussed herein. Further, details of the electronic device 100 that areshown and/or described herein will be understood to apply equally to theelectronic device 800. For example, device components (e.g., attachmentmechanisms, housings, antennas, etc.), application software, graphicaluser interfaces, etc., may all be embodied by the device 800. Further,any of the components, hardware, software, or other systems orcomponents described with respect to the electronic device 800 mayequally be included in the electronic device 100.

As shown in FIG. 8 , a device 800 includes a processing unit 802operatively connected to computer memory 804 and/or computer-readablemedia 806. The processing unit 802 may be operatively connected to thememory 804 and computer-readable media 806 components via an electronicbus or bridge. The processing unit 802 may include one or more computerprocessors or microcontrollers that are configured to perform operationsin response to computer-readable instructions. The processing unit 802may include the central processing unit (CPU) of the device.Additionally or alternatively, the processing unit 802 may include otherprocessors within the device including application specific integratedchips (ASIC) and other microcontroller devices.

The memory 804 may include a variety of types of non-transitorycomputer-readable storage media, including, for example, read accessmemory (RAM), read-only memory (ROM), erasable programmable memory(e.g., EPROM and EEPROM), or flash memory. The memory 804 is configuredto store computer-readable instructions, sensor values, and otherpersistent software elements. Computer-readable media 806 also includesa variety of types of non-transitory computer-readable storage mediaincluding, for example, a hard-drive storage device, a solid-statestorage device, a portable magnetic storage device, or other similardevice. The computer-readable media 806 may also be configured to storecomputer-readable instructions, sensor values, and other persistentsoftware elements.

In this example, the processing unit 802 is operable to readcomputer-readable instructions stored on the memory 804 and/orcomputer-readable media 806. The computer-readable instructions may beprovided as a computer-program product, software application, or thelike.

As shown in FIG. 8 , the device 800 also includes a display 808. Thedisplay 808 may include a liquid-crystal display (LCD), organic lightemitting diode (OLED) display, light emitting diode (LED) display, orthe like. If the display 808 is an LCD, the display 808 may also includea backlight component that can be controlled to provide variable levelsof display brightness. If the display 808 is an OLED or LED typedisplay, the brightness of the display 808 may be controlled bymodifying the electrical signals that are provided to display elements.The display 808 may correspond to any of the displays shown or describedherein, such as the display 104 (FIG. 1A).

The device 800 may also include a battery 809 that is configured toprovide electrical power to the components of the device 800. Thebattery 809 may include one or more power storage cells that are linkedtogether to provide an internal supply of electrical power. The battery809 may be operatively coupled to power management circuitry that isconfigured to provide appropriate voltage and power levels forindividual components or groups of components within the device 800. Thebattery 809, via power management circuitry, may be configured toreceive power from an external source, such as an AC power outlet, acharging dock (e.g., the wireless charging dock 200, FIGS. 2A-2B), anauxiliary battery, a battery-enabled protective case, or the like. Thebattery 809 may store received power so that the device 800 may operatewithout connection to an external power source for an extended period oftime, which may range from several hours to several days. Powermanagement circuitry may include wireless charging components, such as acharging coil that inductively couples to an output coil of a wirelesscharger to charge the battery 809.

In some embodiments, the device 800 includes one or more input devices810. An input device 810 is a device that is configured to receive userinput. The one or more input devices 810 may include, for example, arotatable input system, a push button, a touch-activated button, akeyboard, a key pad, or the like (including any combination of these orother components). In some embodiments, the input device 810 may providea dedicated or primary function, including, for example, a power button,volume buttons, home buttons, scroll wheels, and camera buttons.

The device 800 may also include a sensor 824. The sensor 824 may detectinputs provided by a user to one or more of the input devices 810 of thedevice 800. The sensor 824 may also be a biometric sensor, such as aheart rate sensor, electrocardiograph sensor, temperature sensor, or anyother type of sensor. In cases where the sensor 824 is a biometricsensor, it may include biometric sensing circuitry, as well as portionsof a crown that conductively couple a user's body to the biometricsensing circuitry. Biometric sensing circuitry may include componentssuch as processors, capacitors, inductors, transistors,analog-to-digital converters, or the like.

The device 800 may also include a touch sensor 820 that is configured todetermine a location of a touch on a touch-sensitive surface of thedevice 800 (e.g., an input surface defined by the transparent cover105). The touch sensor 820 may use or include capacitive sensors,resistive sensors, surface acoustic wave sensors, piezoelectric sensors,strain gauges, or the like. In some cases the touch sensor 820associated with a touch-sensitive surface of the device 800 may includea capacitive array of electrodes or nodes that operate in accordancewith a mutual-capacitance or self-capacitance scheme. The touch sensor820 may be integrated with one or more layers of a display stack (e.g.,the display 104, FIG. 1A) to provide the touch-sensing functionality ofa touchscreen.

The device 800 may also include a force sensor 822 that is configured toreceive and/or detect force inputs applied to a user input surface ofthe device 800 (e.g., a surface of the transparent cover 105). The forcesensor 822 may use or include capacitive sensors, resistive sensors,surface acoustic wave sensors, piezoelectric sensors, strain gauges, orthe like. In some cases, the force sensor 822 may include or be coupledto capacitive sensing elements that facilitate the detection of changesin relative positions of the components of the force sensor (e.g.,deflections caused by a force input). The force sensor 822 may beintegrated with one or more layers of a display stack (e.g., the display104) to provide force-sensing functionality of a touchscreen.

The device 800 may also include a communication port 828 that isconfigured to transmit and/or receive signals or electricalcommunication from an external or separate device. The communicationport 828 may be configured to couple to an external device via a cable,adaptor, or other type of electrical connector. In some embodiments, thecommunication port 828 may be used to couple the device 800 to anaccessory, including a dock or case, a stylus or other input device,smart cover, smart stand, keyboard, or other device configured to sendand/or receive electrical signals.

The device 800 may also include a near-field wireless communicationsystem 812 (which may correspond to the near-field wirelesscommunication system 106 in FIG. 1A). The near-field wirelesscommunication system may include one or more antennas and associatedcircuitry for detecting the presence of near-field wirelesscommunication antennas. The near-field wireless communication system 812may be configured to operate using any suitable type or protocol ofnear-field wireless communications, including but not limited tonear-field communications (“NFC”) protocols, radio frequencyidentification (“RFID”) protocols, or any other suitable type orprotocol. The near-field wireless communication system 812 may beconfigured to detect near-field wireless communication antennas througha single side of the device (e.g., the back side), or multiple sides(e.g., any combination of sides including all sides).

While the device 800 is described as having a particular set ofcomponents, the device 800 is not limited to only those componentsdescribed herein. For example, a device may include more than one of thecomponents described with respect to FIG. 8 or elsewhere in the instantapplication, and may indeed include other components not describedherein.

The foregoing description shows and describes various types of graphicalobjects that may be displayed by a device in response to the devicedetecting that it is being used with a near-field wireless enabledaccessory. The graphical objects may take the form of or include icons,graphical user interfaces, background images, notification object (e.g.,for temporary notifications), or the like. The graphical objects may beprogrammatically associated with any suitable application, program, oroperating system of the device, and/or may originate from any suitablelayer of the Open Systems Interconnection model (OSI model). Forexample, in cases where the device detects an accessory and in responsetemporarily displays a notification object over a part of a primarygraphical user interface of an operating system, the notification objectmay be programmatically associated with or originate from the operatingsystem. As another example, in cases where the device detects anaccessory and in response initiates an application, the graphical userinterface of the application may be programmatically associated with ororiginate from the application (where an application may be defined as asoftware program that is executed by or on the operating system).

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve theusefulness of the devices described herein. The present disclosurecontemplates that in some instances, this gathered data may includepersonal information data that uniquely identifies or can be used tocontact or locate a specific person. Such personal information data caninclude demographic data, location-based data, telephone numbers, emailaddresses, twitter ID's, home addresses, data or records relating to auser's health or level of fitness (e.g., vital signs measurements,medication information, exercise information), date of birth, or anyother identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used to thebenefit of users. For example, the personal information data can be usedto provide customized graphical user interfaces and user experiences.Further, other uses for personal information data that benefit the userare also contemplated by the present disclosure. For instance, healthand fitness data may be used to provide insights into a user's generalwellness, or may be used as positive feedback to individuals usingtechnology to pursue wellness goals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof advertisement delivery services, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services or anytime thereafter. In addition toproviding “opt in” and “opt out” options, the present disclosurecontemplates providing notifications relating to the access or use ofpersonal information. For instance, a user may be notified upondownloading an app that their personal information data will be accessedand then reminded again just before personal information data isaccessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thecontent delivery services, or publicly available information.

As used herein, the phrase “at least one of” preceding a series ofitems, with the term “and” or “or” to separate any of the items,modifies the list as a whole, rather than each member of the list. Thephrase “at least one of” does not require selection of at least one ofeach item listed; rather, the phrase allows a meaning that includes at aminimum one of any of the items, and/or at a minimum one of anycombination of the items, and/or at a minimum one of each of the items.By way of example, the phrases “at least one of A, B, and C” or “atleast one of A, B, or C” each refer to only A, only B, or only C; anycombination of A, B, and C; and/or one or more of each of A, B, and C.Similarly, it may be appreciated that an order of elements presented fora conjunctive or disjunctive list provided herein should not beconstrued as limiting the disclosure to only that order provided.

The foregoing description, for purposes of explanation, used specificnomenclature to provide a thorough understanding of the describedembodiments. However, it will be apparent to one skilled in the art thatthe specific details are not required in order to practice the describedembodiments. Thus, the foregoing descriptions of the specificembodiments described herein are presented for purposes of illustrationand description. They are not targeted to be exhaustive or to limit theembodiments to the precise forms disclosed. It will be apparent to oneof ordinary skill in the art that many modifications and variations arepossible in view of the above teachings. Also, when used herein to referto positions of components, the terms above and below, or theirsynonyms, do not necessarily refer to an absolute position relative toan external reference, but instead refer to the relative position ofcomponents with reference to the figures.

What is claimed is:
 1. A system comprising: an electronic devicecomprising: an enclosure comprising a transparent cover; a displaypositioned below the transparent cover and configured to display a firstgraphical output and a second graphical output different from the firstgraphical output; and a touch sensor positioned below the transparentcover and configured to detect a touch input applied to the transparentcover; and a protective case comprising: a shell defining a cavity andconfigured to at least partially cover the enclosure of the electronicdevice when the electronic device is positioned in the cavity; and anear-field wireless communication antenna coupled to the shell anddetectable by the electronic device, wherein: in response to detectingthe near-field wireless communication antenna, the electronic device isconfigured to switch from the first graphical output to the secondgraphical output.
 2. The system of claim 1, wherein: the electronicdevice is a mobile phone; the protective case has an exterior surfacehaving a color; the first graphical output includes a group ofapplication icons and has a first color scheme; the second graphicaloutput includes the group of application icons and has a second colorscheme; and the second color scheme is different from the first colorscheme and corresponds to the color of the exterior surface of theprotective case.
 3. The system of claim 1, wherein: the enclosuredefines: a back exterior side of the electronic device; a front exteriorside of the electronic device; and a peripheral exterior side of theelectronic device, the peripheral exterior side extending from the backexterior side to the front exterior side; and the shell further defines:a window region configured to allow a user to touch the front exteriorside of the electronic device when the electronic device is positionedin the cavity; a back wall configured to at least partially cover theback exterior side of the electronic device; and a side wall configuredto at least partially cover the peripheral exterior side of theelectronic device.
 4. The system of claim 1, wherein: the protectivecase further comprises an input system comprising: an actuation memberconfigured to be actuated by a user; and a passive antenna; subsequentto detecting the near-field wireless communication antenna and inresponse to the actuation member being actuated by the user, the passiveantenna becomes detectable by the electronic device; and the electronicdevice is configured to execute an operation in response to detectingthe passive antenna.
 5. The system of claim 4, wherein the passiveantenna is not detectable by the electronic device when the actuationmember is unactuated.
 6. The system of claim 4, wherein: the electronicdevice further comprises a camera system; the second graphical outputcorresponds to an image-capture interface; and actuation of theactuation member causes the electronic device to capture an image usingthe camera system.
 7. The system of claim 1, wherein: the firstgraphical output includes a first background image; and the secondgraphical output includes a second background image different from thefirst background image.
 8. A dock for an electronic device, comprising:a support structure configured to position the electronic device in aviewable orientation; a near-field wireless communication antennadetectable by the electronic device when the electronic device ispositioned on the support structure, the electronic device configured todisplay a graphical user interface in response to detecting thenear-field wireless communication antenna; and an input systemconfigured to wirelessly communicate with the electronic device inresponse to the input system being actuated while the electronic deviceis positioned on the support structure.
 9. The dock of claim 8, wherein:the input system comprises: an actuation member; and a passive antenna;and in response to the actuation member being actuated by a user, theinput system wirelessly communicates with the electronic device usingthe passive antenna.
 10. The dock of claim 8, wherein: the graphicaluser interface is a secondary graphical user interface; and theelectronic device is configured to switch from displaying the secondarygraphical user interface to displaying a primary graphical userinterface in response to being removed from the support structure. 11.The dock of claim 8, wherein: the graphical user interface correspondsto an alarm clock function of the electronic device; and actuation ofthe input system causes the electronic device to change a setting of thealarm clock function.
 12. The dock of claim 8, wherein: the dock furthercomprises a speaker; the graphical user interface corresponds to anaudio playback function of the electronic device; and actuation of theinput system causes the electronic device to change an operationalparameter of the audio playback function.
 13. The dock of claim 8,further comprising a wireless charging system comprising an output coilconfigured to inductively couple to a charging coil of the electronicdevice when the electronic device is held by the support structure. 14.A handheld electronic device comprising: an enclosure; a display; atouch sensor positioned within the enclosure; and a near-field wirelesscommunication system configured to detect when the handheld electronicdevice is in proximity to any one of a set of docking accessories,wherein: when the near-field wireless communication system detects thatthe handheld electronic device is in proximity to a first dockingaccessory of the set of docking accessories, the handheld electronicdevice transitions from a first mode of operation to a second mode ofoperation different from the first mode of operation; and when thenear-field wireless communication system detects that the handheldelectronic device is in proximity to a second docking accessory of theset of docking accessories, the handheld electronic device transitionsfrom the first mode of operation to a third mode of operation differentfrom the first mode of operation and from the second mode of operation.15. The handheld electronic device of claim 14, wherein: the firstdocking accessory is in a first location; the second docking accessoryis in a second location different from the first location; transitioningfrom the first mode of operation to the second mode of operationcomprises transitioning from displaying a primary graphical userinterface comprising a set of application icons to displaying a firstauxiliary graphical user interface comprising a first set of graphicalobjects that are relevant to the first location; and transitioning fromthe first mode of operation to the third mode of operation comprisestransitioning from displaying the primary graphical user interface todisplaying a second auxiliary graphical user interface different fromthe first auxiliary graphical user interface and comprising a second setof graphical objects that are relevant to the second location.
 16. Thehandheld electronic device of claim 14, wherein: transitioning from thefirst mode of operation to the second mode of operation comprisestransitioning from displaying a primary graphical user interface todisplaying a first auxiliary graphical user interface; and transitioningfrom the first mode of operation to the third mode of operationcomprises transitioning from displaying the primary graphical userinterface to displaying a second auxiliary graphical user interfacedifferent from the first auxiliary graphical user interface.
 17. Thehandheld electronic device of claim 16, wherein: the first auxiliarygraphical user interface comprises a first user-defined set of graphicalobjects selected from a group of candidate graphical objects; and thesecond auxiliary graphical user interface comprises a seconduser-defined set of graphical objects selected from the group ofcandidate graphical objects.
 18. The handheld electronic device of claim17, wherein the first user-defined set of graphical objects includes anaudio control input object.
 19. The handheld electronic device of claim18, wherein the second user-defined set of graphical objects lacks theaudio control input object.
 20. The handheld electronic device of claim17, wherein the first user-defined set of graphical objects are arrangedon the display according to a user-defined arrangement.